-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm start fails after copying a generated project to a new directory #200
Comments
Manually running the
Oddly, when comparing the 2 projects side-by-side, the
|
I was intrigued so I dug into this real quick. The problem is that
However,
Looks like I'm not sure that this can really be resolved by |
I’ll close because this is not actionable for us—it’s just how |
Same problem here |
|
@kenkoooo Thank you so much your solution worked perfectly! |
@kenkoooo Thanks again you solution fix my app. |
@kenkoooo Thank you! |
Facing the same issue! But any of above mentioned solutions didn't work for me. I'm on Ubuntu 16.04. |
If npm is failing it's worth giving yarn a try. I had a few intermittent npm failures on our CI server at one point, and switching to yarn solved them. |
@allpratik If you have a
|
Also if you use npm 5.x, downgrade to 4.x.
npm 5.x has many known issues right now and is buggy. |
I upgraded to npm 5.1.0 and it fixed the problem for me. I blew out my |
Please help me :( 0 info it worked if it ends with ok |
I faced this problem when moving from
solved it |
If you change node_modules directory you have to change paths also inside node_modules/* package.json files. Search and replace \old_path to new one. If you want to change /src path then modify react-scripts/config/paths.js |
thanks,it is save me |
@latentflip You are really right, thank you very much. So many people just said the solution while you told us the truth. |
@kenkoooo Thanks it worked for me. |
yeah |
Just wanted this. |
I just ran into this error when copying the create-react-app contents to a new directory.
|
Here is the failure:
To reproduce:
At first I thought it might have something to do with having run
npm start
from withinbug-test
before copying it, but skipping that step didn't have any effect.Removing
node_modules
and reinstalling them fixes it:Using
cp -a
instead ofcp -r
does not cause the problem:I'm running Node 5.0.0 and npm 3.3.12.
I tried (via nvm) with Node 6.3.1 and npm 3.10.3 and got the same behavior.
The
cp -a
vscp -r
makes me think this might be an npm bug.The text was updated successfully, but these errors were encountered: