Error: Cannot find module 'C:\WorkPlace\moo\iyin\node_modules\react-scripts\package.json

[starerp-ai]

If you are reporting a bug, please fill in below. Otherwise feel to remove this template entirely.

Description

Error: Cannot find module 'C:\WorkPlace\moo\iyin\node_modules\react-scripts\package.json

Expected behavior

install create-react-app successfully

Actual behavior

installation failed

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected): [email protected]
2. node -v: v6.5.0
3. npm -v:3.10.3

Then, specify:

1. Operating system:win 10
2. Browser and version: chrome

[amilajack]

Try manually checking if the file exists. If it doesnt exist, that's probably a bug

[starerp-ai]

There is only one file in the project directory generated by CLI,
which is package.json
the content of this file is below:
{
"name": "test",
"version": "0.1.0",
"private": true
}

[gaearon]

This means your installation failed (or something interrupted it). Maybe there was a network failure. Try running create-react-app again and make sure it finishes successfully. If it doesn't work please paste the complete output from that command.

[starerp-ai]

still not work!

[gaearon]

Could this be related? Can you try solutions in this question?

http://stackoverflow.com/questions/19569990/npm-install-doesnt-work-in-windows-powershell

[gaearon]

Does a file called c:\package.json exist?

[starerp-ai]

package.json does not exist in C:
npm works normally except for this case.

[gaearon]

Can you try creating a project anywhere else on the disk?

[starerp-ai]

I have tried creating projects in different directories many times, same error reported

[amilajack]

Last resort would be to use something like Docker or vagrant

[gaearon]

Can you try updating npm? Might be some bug.

npm i -g npm@next

[starerp-ai]

npm updated, still not work.

I saw react-scripts/package.json is generated in C:\node_modules,
not in C:\react1\node_modules which is expected to be here.

[gaearon]

This is interesting. Can you look into why this happens?

[gaearon]

Closing as it appears that this is some kind of localized issue happening with your npm setup. I’m happy to reopen if you could look into why this happens and provide some hints, or if more users hit this. At the moment it doesn’t appear very actionable for us, unfortunately.