create-react-app failing

[anilpank]

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

Can you reproduce the problem with latest npm?

Many errors, especially related to "missing modules", are due to npm bugs.

If you're using Windows, follow these instructions to update npm.

If you're using OS X or Linux, run this to update npm:

npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.

Can you still reproduce it?
Yes

Description

I am trying to use create-react-app to create a react app using command create-react-app work. My OS is Windows 7 64 bit, npm version is 4.5.0, node version is v7.8.0, I tried with earlier npm and node versions as well and still unable to use create-react-app

What are you reporting?

Expected behavior

The command above should be able to create react app.
Tell us what you think should happen.

Actual behavior

Tell us what actually happens.
It aborts with following messages.
npm WARN prefer global marked@0.3.6 should be installed with -g
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.17 (node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
Aborting installation.
npm install --save --save-exact react react-dom react-scripts has failed.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting work/ from C:\anil\business
Done.

Environment

Windows 7 64 bit
Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected):
   C:\anil\business
   `-- (empty)

2. node -v:
   v7.8.0

3. npm -v:
   4.5.0

Then, specify:

1. Operating system:
   Windows
2. Browser and version:
   NA

Reproducible Demo

Please take the time to create a new app that reproduces the issue.

Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.

(Accidentally, you might get to the root of your problem during that process.)

log.txt

Push to GitHub and paste the link here.

By doing this, you're helping the Create React App contributors a big time!
Demonstrable issues gets fixed faster.

[gaearon]

Can you post output of create-react-app --version?

[anilpank]

1.3.0

[gaearon]

We made a mistake of deleting npm log files so we can't really tell what happened 😞

I think we should remove *.log files from this line and instead add them here. This way you'll have the log file remaining in the folder that would tell us what went wrong.

Can you try to do these changes to your local create-react-app (run which create-react-app to learn where it is) and then post npm-debug.log in the folder?

Sorry for the trouble.

[anilpank]

I did the above changes and could not see any files generated. Looks like I have to finally learn webpack :(

[gaearon]

Well, the issue is clearly with npm. Can you run

mkdir test
cd test
npm i react-scripts react react-dom

and post the output? I'd assume it would also fail.

[anilpank]

I ran the above commands and did not see any error. A folder called node_modules was created with various modules and a .bin folder. I got the following warnings, but overall the operation was successful
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.17 (node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'C:\anil\business\gargi\test\package.json'
npm WARN test No description
npm WARN test No repository field.
npm WARN test No README data
npm WARN test No license field.

[gaearon]

Okay, thanks for trying.
Can you put a console.log before this line?

    child.on('close', function(code) {
      console.log(code); // <--- add this
      if (code !== 0) {
        reject({
          command: command + ' ' + args.join(' ')
        });
        return;
      }
      resolve();
    });

and try again?

[gaearon]

Actually can I ask you to run create-react-app qwerty --verbose? I forgot we have this flag.
Then could you paste the output in a gist and link it from here.

[anilreddykatta]

@anilpank I guess issue is with fsevents, I have encountered same problem in windows while working on different package.

gulpjs/gulp#1810

[Kaplaugher]

I have the exact same problem =(

[gaearon]

I guess issue is with fsevents, I have encountered same problem in windows while working on different package.

It’s not an issue though. npm warns about an optional dependency, but it should not cause any errors. We have a continuous integration test that runs on Windows, and it works fine.

If you still have issues please run the command with --verbose flag as I asked earlier, and provide the output. Thanks!

[SeducerStar]

I have the same problem. How can I fix this? node -v 7.10.0 npm -v 4.2.0

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.17 (node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux
npm verb notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
npm verb stack Error: EPROTO: protocol error, symlink '../acorn/bin/acorn' -> '/app/my-react/node_modules/.bin/acorn'
npm verb cwd /app/my-react
npm ERR! Linux 4.4.27-boot2docker
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save" "--save-exact" "react" "react-dom" "react-scripts" "--verbose"
npm ERR! node v7.10.0
npm ERR! npm v4.2.0
npm ERR! path ../acorn/bin/acorn
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! syscall symlink

npm ERR! EPROTO: protocol error, symlink '../acorn/bin/acorn' -> '/app/my-react/node_modules/.bin/acorn'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm verb exit [ -71, true ]

npm ERR! Please include the following file with any support request:
npm ERR! /root/.npm/_logs/2017-05-13T07_33_06_892Z-debug.log

Aborting installation.
npm install --save --save-exact react react-dom react-scripts --verbose has failed.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting my-react/ from /app
Done.

[viankakrisna]

@SeducerStar based on this

npm ERR! EPROTO: protocol error, symlink '../acorn/bin/acorn' -> '/app/my-react/node_modules/.bin/acorn'

npm fails to create a symlink for acorn. Do you run create-react-app in a linux vm for a shared folder in a windows host?

edit:
Looking at this

npm ERR! Linux 4.4.27-boot2docker
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save" "--save-exact" "react" 

it seems likely that it is.

try to run it with node in your host machine. AFAIK symlinking in a shared folder from windows will cause this Error: EPROTO: protocol error,

[SeducerStar]

@viankakrisna
yes! I use docker.