If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.
Yes
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...
> [email protected] 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 [email protected] and [email protected] (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
Should not get this output.
Tell us what actually happens.
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.2npm -v:
4.6.1 - the problem also occurs with v 5.
Then, specify:
Operating system:
macOS Sierra version 10.12.5
Any invocation of create-react-app results in this output.
with npm@5 the output is somewhat different:
Installing packages. This might take a couple minutes.
Installing react-scripts...
> [email protected] 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 [email protected]
node-pre-gyp info using [email protected] | 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 [email protected] and [email protected] (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
Have you tried with Node 7?
It seems that version 7 isn’t supported by brew, the mac package manager that I use.
https://github.com/Homebrew/homebrew-core/issues/14118 https://github.com/Homebrew/homebrew-core/issues/14118
Do you have reason to believe that version 7 would fix the problem?
On Jun 25, 2017, at 11:13 AM, Dan Abramov notifications@github.com 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 https://github.com/facebookincubator/create-react-app/issues/2613#issuecomment-310911953, or mute the thread https://github.com/notifications/unsubscribe-auth/AAoGahfcA2LxNZb4MlkX8VbvhBI90qBOks5sHocwgaJpZM4OEoh0.
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.
This is a specific-to Node 8 issue and was resolved via PR https://github.com/facebookincubator/create-react-app/pull/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.
Getting the same issue:
Windows 10
7.2.1
5.0.3
λ 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...
> [email protected] 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 [email protected]
node-pre-gyp info using [email protected] | 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 [email protected] and [email protected] (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 )
@LeeCheneler
Please downgrade to npm to npm 4 and try again:
npm i -g npm@4
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...
> [email protected] 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 [email protected] and [email protected] (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
[email protected] /Users/charlesirvine/src/react/tinymce-editor
Hmm. The log says:
Pre-built binaries not found for [email protected] and [email protected]
I wonder why, given that you say you're trying with Node 7.
No, I am using node@8. I haven't used version 7 since it's not supported by brew, the Mac package manager.
Ah sorry, I thought I was replying to previous poster.
Yes, this error is expected with Node 8. As noted in https://github.com/facebookincubator/create-react-app/issues/2613#issuecomment-310917190, it's a known issue we're working to fix.
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 [email protected] and [email protected] (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 [email protected] and I am able to run $create-react-app fine now.
If I run :
sudo npm -i -g [email protected]
and then run create-react-app errors turn into warnings, I get :
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: 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 [email protected]: 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.
It will work fine. fsevents is only needed on macOS. Unfortunately npm produces a noisy warning, but in practice this is working as intended.
Going to hide those nasty warnings 😛
https://github.com/facebookincubator/create-react-app/pull/2635
The error was solved by https://github.com/facebookincubator/create-react-app/pull/2550.
The warning was solved by https://github.com/facebookincubator/create-react-app/pull/2635.
Closing.
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!
I'll cut a fix tomorrow. It's only in master, but not released yet.
Fixed in 1.0.8. Please verify.
https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.8
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...
[email protected] 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
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 notifications@github.com 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.