create-react-app issue related to fsevents@1.0.17 #2613

CharlesIrvineKC · 2017-06-25T15:14:32Z

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

Can you reproduce the problem with npm 4.x?

Yes

Description

When running create-react-app I get:

Creating a new React app in /Users/charlesirvine/tmp/slate-editor.

Installing packages. This might take a couple minutes.
Installing react-scripts...


> fsevents@1.0.17 install /Users/charlesirvine/tmp/slate-editor/node_modules/fsevents
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.17 and node@8.1.2 (node-v57 ABI) (falling back to source compile with node-gyp) 
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  COPY /Users/charlesirvine/tmp/slate-editor/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp

Expected behavior

Should not get this output.

Actual behavior

Tell us what actually happens.

Environment

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

npm ls react-scripts (if you haven’t ejected):

~/tmp $ npm ls react-scripts
/Users/charlesirvine
└── (empty)

node -v:
v8.1.2
npm -v:
4.6.1 - the problem also occurs with v 5.
Then, specify:
Operating system:
macOS Sierra version 10.12.5
Browser and version:
na

Reproducible Demo

Any invocation of create-react-app results in this output.

The text was updated successfully, but these errors were encountered:

CharlesIrvineKC · 2017-06-25T15:20:54Z

with npm@5 the output is somewhat different:

Installing packages. This might take a couple minutes.
Installing react-scripts...


> fsevents@1.0.17 install /Users/charlesirvine/tmp/slate-editor/node_modules/fsevents
> node-pre-gyp install --fallback-to-build

node-pre-gyp info it worked if it ends with ok
node-pre-gyp verb cli [ '/usr/local/Cellar/node/8.1.2/bin/node',
node-pre-gyp verb cli   '/Users/charlesirvine/tmp/slate-editor/node_modules/fsevents/node_modules/.bin/node-pre-gyp',
node-pre-gyp verb cli   'install',
node-pre-gyp verb cli   '--fallback-to-build' ]
node-pre-gyp info using node-pre-gyp@0.6.32
node-pre-gyp info using node@8.1.2 | darwin | x64
node-pre-gyp verb command install []
node-pre-gyp info check checked for "/Users/charlesirvine/tmp/slate-editor/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.17 and node@8.1.2 (node-v57 ABI) (falling back to source compile with node-gyp) 
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz 
node-pre-gyp verb command build [ 'rebuild' ]
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  COPY /Users/charlesirvine/tmp/slate-editor/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp
node-pre-gyp info ok

gaearon · 2017-06-25T16:13:22Z

Have you tried with Node 7?

CharlesIrvineKC · 2017-06-25T16:25:52Z

It seems that version 7 isn’t supported by brew, the mac package manager that I use. Homebrew/homebrew-core#14118 <Homebrew/homebrew-core#14118> Do you have reason to believe that version 7 would fix the problem?

…

On Jun 25, 2017, at 11:13 AM, Dan Abramov ***@***.***> wrote: Have you tried with Node 7? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2613 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAoGahfcA2LxNZb4MlkX8VbvhBI90qBOks5sHocwgaJpZM4OEoh0>.

gaearon · 2017-06-25T16:49:53Z

Since it used to not be a problem and Node 8 came out recently I am assuming this might be a Node 8 specific regression.

Timer · 2017-06-25T17:48:13Z

This is a specific-to Node 8 issue and was resolved via PR #2550. Just pending release afaik, but we should probably test it actually fixes it.

Basically, Node 8 builds are only available on newer versions of fsevents.

LeeCheneler · 2017-06-25T18:27:30Z

Getting the same issue:

OS

Windows 10

Node Version

7.2.1

NPM Version

5.0.3

CMD output

λ create-react-app test                                                                                                                                                                                            
Creating a new React app in C:\projects\test.                                                                                                                                                                      
                                                                                                                                                                                                                   
Installing packages. This might take a couple minutes.                                                                                                                                                             
Installing react, react-dom, and react-scripts...                                                                                                                                                                  
                                                                                                                                                                                                                   
                                                                                                                                                                                                                   
> fsevents@1.0.17 install C:\projects\test\node_modules\fsevents                                                                                                                                                   
> node-pre-gyp install --fallback-to-build                                                                                                                                                                         
                                                                                                                                                                                                                   
node-pre-gyp info it worked if it ends with ok                                                                                                                                                                     
node-pre-gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe',                                                                                                                                                     
node-pre-gyp verb cli   'C:\\projects\\test\\node_modules\\fsevents\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp',                                                                                               
node-pre-gyp verb cli   'install',                                                                                                                                                                                 
node-pre-gyp verb cli   '--fallback-to-build' ]                                                                                                                                                                    
node-pre-gyp info using node-pre-gyp@0.6.32                                                                                                                                                                        
node-pre-gyp info using node@7.2.1 | win32 | x64                                                                                                                                                                   
node-pre-gyp verb command install []                                                                                                                                                                               
node-pre-gyp info check checked for "C:\projects\test\node_modules\fsevents\lib\binding\Release\node-v51-win32-x64\fse.node" (not found)                                                                           
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v51-win32-x64.tar.gz                                                                                           
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v51-win32-x64.tar.gz                                                                                           
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v51-win32-x64.tar.gz                                                                       
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.17 and node@7.2.1 (node-v51 ABI) (falling back to source compile with node-gyp)                                                                    
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v51-win32-x64.tar.gz                                                           
node-pre-gyp verb command build [ 'rebuild' ]                                                                                                                                                                      
                                                                                                                                                                                                                   
C:\projects\test\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\Lee Cheneler\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" clean ) 
 else (node "" clean )                                                                                                                                                                                             
                                                                                                                                                                                                                   
C:\projects\test\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\Lee Cheneler\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" configur
e --fallback-to-build --module=C:\projects\test\node_modules\fsevents\lib\binding\Release\node-v51-win32-x64\fse.node --module_name=fse --module_path=C:\projects\test\node_modules\fsevents\lib\binding\Release\no
de-v51-win32-x64 )  else (node "" configure --fallback-to-build --module=C:\projects\test\node_modules\fsevents\lib\binding\Release\node-v51-win32-x64\fse.node --module_name=fse --module_path=C:\projects\test\no
de_modules\fsevents\lib\binding\Release\node-v51-win32-x64 )

gaearon · 2017-06-26T10:20:56Z

@LeeCheneler

Please downgrade to npm to npm 4 and try again:

npm i -g npm@4

CharlesIrvineKC · 2017-06-26T17:35:59Z

I down graded to version 4 as the first step in creating this ticket. The output using npm@4 is shown below. Notice that it is somewhat different than the output for npm@5.

Installing packages. This might take a couple minutes.
Installing react-scripts...


> fsevents@1.0.17 install /Users/charlesirvine/src/react/tinymce-editor/node_modules/fsevents
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v57-darwin-x64.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.17 and node@8.1.2 (node-v57 ABI) (falling back to source compile with node-gyp) 
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  COPY /Users/charlesirvine/src/react/tinymce-editor/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp
tinymce-editor@0.1.0 /Users/charlesirvine/src/react/tinymce-editor

gaearon · 2017-06-26T18:01:18Z

Hmm. The log says:

Pre-built binaries not found for fsevents@1.0.17 and node@8.1.2

I wonder why, given that you say you're trying with Node 7.

CharlesIrvineKC · 2017-06-26T18:20:37Z

No, I am using node@8. I haven't used version 7 since it's not supported by brew, the Mac package manager.

gaearon · 2017-06-26T18:21:57Z

Ah sorry, I thought I was replying to previous poster.

Yes, this error is expected with Node 8. As noted in #2613 (comment), it's a known issue we're working to fix.

juancortez · 2017-06-26T21:22:59Z

Having a similar issue.

node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v48-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.17 and node@6.11.0 (node-v48 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.17/fse-v1.0.17-node-v48-win32-x64.tar.gz
node-pre-gyp verb command build [ 'rebuild' ]

It might be an npm problem. I was having this problem and just ran $npm i -g npm@3.10.8 and I am able to run $create-react-app fine now.

dparkar · 2017-06-27T10:14:24Z

If I run :

sudo npm -i -g npm@3.10.8

and then run create-react-app errors turn into warnings, I get :

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 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.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

Please note that, running create-react-app with latest npm does produce the react folder structure and I can run npm start which opens the starter app in the browser correctly. Since I am new to react, I am not sure what will not work without fsevents.

gaearon · 2017-06-27T10:52:59Z

It will work fine. fsevents is only needed on macOS. Unfortunately npm produces a noisy warning, but in practice this is working as intended.

gaearon · 2017-06-27T14:37:22Z

Going to hide those nasty warnings 😛
#2635

gaearon · 2017-06-27T14:41:28Z

The error was solved by #2550.
The warning was solved by #2635.

Closing.

yenly · 2017-06-27T18:13:30Z

Hi all,
Love the quick response and fix. I'm new to OSS and to react dev. Big fan of all the tooling you're all building. I see a fix is checked it. How do I get this update on my local create-react-app env to use? Thanks in advance!

gaearon · 2017-06-27T20:50:15Z

I'll cut a fix tomorrow. It's only in master, but not released yet.

gaearon · 2017-06-28T16:42:29Z

Fixed in 1.0.8. Please verify.
https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.8

CharlesIrvineKC · 2017-06-28T17:39:59Z

Yep, looks much better. The output is now is given below. Thanks!! Installing packages. This might take a couple of minutes. Installing react, react-dom, and react-scripts...

***@***.*** install /Users/charlesirvine/src/react/tmp/node_modules/fsevents node install

[fsevents] Success: "/Users/charlesirvine/src/react/tmp/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed Pass --update-binary to reinstall or --build-from-source to recompile + react@15.6.1 + react-dom@15.6.1 + react-scripts@1.0.8 added 1208 packages in 66.382s Success! Created tmp at /Users/charlesirvine/src/react/tmp Inside that directory, you can run several commands: npm start Starts the development server. npm run build Bundles the app into static files for production. npm test Starts the test runner. npm run eject Removes this tool and copies build dependencies, configuration files and scripts into the app directory. If you do this, you can’t go back! We suggest that you begin by typing: cd tmp npm start

…

On Jun 28, 2017, at 11:42 AM, Dan Abramov ***@***.***> wrote: Fixed in 1.0.8. Please verify. https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.8 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

This fixes the following error on macOS with regards to and fsevents@1.0.17 not being found when using Node.js 8+. See issues and pull requests: facebook/create-react-app#2613 facebook/create-react-app#2550 fsevents/fsevents#170 fsevents/fsevents#169. A minimum verison of v1.0.8 is required as the PR was pushed in that release: https://github.com/facebook/create-react-app/releases/tag/v1.0.8 Considering the targeted nature of the project, I figured that upgrading to the latest (v1.1.1) would be safe.

gaearon added the issue: bug label Jun 26, 2017

gaearon added this to the 1.0.x milestone Jun 26, 2017

gaearon mentioned this issue Jun 27, 2017

Set npm loglevel to 'error' #2635

Merged

gaearon closed this as completed Jun 27, 2017

gaearon modified the milestones: 1.0.8, 1.0.x Jun 27, 2017

hysan mentioned this issue Feb 22, 2018

Upgraded react-scripts dependency to the latest v1.1.1. learn-co-curriculum/instructor-code-challenge#1

Open

lock bot locked and limited conversation to collaborators Jan 21, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

create-react-app issue related to fsevents@1.0.17 #2613

create-react-app issue related to fsevents@1.0.17 #2613

CharlesIrvineKC commented Jun 25, 2017

CharlesIrvineKC commented Jun 25, 2017

gaearon commented Jun 25, 2017

CharlesIrvineKC commented Jun 25, 2017 via email

gaearon commented Jun 25, 2017

Timer commented Jun 25, 2017 •

edited

LeeCheneler commented Jun 25, 2017 •

edited

gaearon commented Jun 26, 2017

CharlesIrvineKC commented Jun 26, 2017

gaearon commented Jun 26, 2017

CharlesIrvineKC commented Jun 26, 2017

gaearon commented Jun 26, 2017

juancortez commented Jun 26, 2017

dparkar commented Jun 27, 2017 •

edited

gaearon commented Jun 27, 2017

gaearon commented Jun 27, 2017

gaearon commented Jun 27, 2017

yenly commented Jun 27, 2017 •

edited

gaearon commented Jun 27, 2017

gaearon commented Jun 28, 2017

CharlesIrvineKC commented Jun 28, 2017 via email

create-react-app issue related to fsevents@1.0.17 #2613

create-react-app issue related to fsevents@1.0.17 #2613

Comments

CharlesIrvineKC commented Jun 25, 2017

Can you reproduce the problem with npm 4.x?

Description

Expected behavior

Actual behavior

Environment

Reproducible Demo

CharlesIrvineKC commented Jun 25, 2017

gaearon commented Jun 25, 2017

CharlesIrvineKC commented Jun 25, 2017 via email

gaearon commented Jun 25, 2017

Timer commented Jun 25, 2017 • edited

LeeCheneler commented Jun 25, 2017 • edited

OS

Node Version

NPM Version

CMD output

gaearon commented Jun 26, 2017

CharlesIrvineKC commented Jun 26, 2017

gaearon commented Jun 26, 2017

CharlesIrvineKC commented Jun 26, 2017

gaearon commented Jun 26, 2017

juancortez commented Jun 26, 2017

dparkar commented Jun 27, 2017 • edited

gaearon commented Jun 27, 2017

gaearon commented Jun 27, 2017

gaearon commented Jun 27, 2017

yenly commented Jun 27, 2017 • edited

gaearon commented Jun 27, 2017

gaearon commented Jun 28, 2017

CharlesIrvineKC commented Jun 28, 2017 via email

Timer commented Jun 25, 2017 •

edited

LeeCheneler commented Jun 25, 2017 •

edited

dparkar commented Jun 27, 2017 •

edited

yenly commented Jun 27, 2017 •

edited