Uh oh!
There was an error while loading. Please reload this page.
Port cra.sh development task to javascript - #2309
Conversation
cr101
commented
May 23, 2017
@ianschmitz Thank you for this PR. A much-needed improvement for the Windows users.
However, after I upgraded Yarn to the current stable version 0.24.5 it then worked fine. |
ianschmitz
commented
May 23, 2017
Yes I found that same behavior as well @cr101. I was running yarn 0.23.4. I mentioned it in the code review. Latest stable fixed it for me |
cr101
commented
Jun 28, 2017
@gaearon I've been using this change on my local Windows 10 dev machine for a couple of months now and it works great. Can this be merged please? |
ianschmitz
commented
Jun 28, 2017
The part I was hoping to get a review on was if the |
ianschmitz
commented
Jul 25, 2017
Seems like this has been used for a while now with good success. Can we get this in soonish? :) |
xjlim
commented
Nov 7, 2017
@Timer this is the PR you mentioned. Can confirm this works 👍 |
Use absolute path when generating .tgz path
ianschmitz
commented
Nov 8, 2017
I just rebased and updated the license comment. Thoughts on the error output? @Timer? |
Timer
commented
Nov 8, 2017
I think the error is fine; this is for local devs so the more information the better. An end user will never see it. |
* Port cra.sh development task to javascript * Port cra.sh development task to javascript Use absolute path when generating .tgz path

I've ported
tasks/cra.shto javascript to make it easier for contributors on Windows based systems to run an end to end create-react-app CLI workflow as discussed in #2280.If someone more familiar with proper handling of child processes and signal events could take a close look that would be much appreciated!
I've tested on Windows 10 using both npm and yarn in Command Prompt, PowerShell and Git Bash.