Yes
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"})
N/A
node -v: 8.0.3npm -v:5.0.3yarn --version (if you use Yarn): 0.22npm ls react-scripts (if you haven鈥檛 ejected):  emptyThen, specify:
npm install -g create-react-appNo installation errors or warnings.
benjamin@thor:~/MY_APPS $ create-react-app my-first-react-app
Creating a new React app in /home/benjamin/MY_APPS/my-first-react-app.
Installing packages. This might take a couple minutes.
Installing react, react-dom, and react-scripts...
> [email protected] install /home/benjamin/MY_APPS/my-first-react-app/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 [ '/home/benjamin/.nvm/versions/node/v8.1.2/bin/node',
node-pre-gyp verb cli   '/home/benjamin/MY_APPS/my-first-react-app/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] | linux | x64
node-pre-gyp verb command install []
node-pre-gyp info check checked for "/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/lib/binding/Release/node-v57-linux-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-linux-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-linux-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-linux-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-linux-x64.tar.gz 
node-pre-gyp verb command build [ 'rebuild' ]
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
make: Entering directory '/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/build'
  SOLINK_MODULE(target) Release/obj.target/.node
  COPY Release/.node
make: Leaving directory '/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/build'
node-pre-gyp info ok 
npm notice created a lockfile as package-lock.json. You should commit this file.
+ [email protected]
+ [email protected]
+ [email protected]
added 1193 packages in 31.426s
No demo created, easy to repro
Do you want to request a feature or report a bug? Report a bug.
What is the current behavior? Receiving errors and warnings while executing the create-react-app ... command
benjamin@thor:~/MY_APPS $ create-react-app my-first-react-app
Creating a new React app in /home/benjamin/MY_APPS/my-first-react-app.
Installing packages. This might take a couple minutes.
Installing react, react-dom, and react-scripts...
> [email protected] install /home/benjamin/MY_APPS/my-first-react-app/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 [ '/home/benjamin/.nvm/versions/node/v8.1.2/bin/node',
node-pre-gyp verb cli   '/home/benjamin/MY_APPS/my-first-react-app/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] | linux | x64
node-pre-gyp verb command install []
node-pre-gyp info check checked for "/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/lib/binding/Release/node-v57-linux-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-linux-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-linux-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-linux-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-linux-x64.tar.gz 
node-pre-gyp verb command build [ 'rebuild' ]
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
make: Entering directory '/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/build'
  SOLINK_MODULE(target) Release/obj.target/.node
  COPY Release/.node
make: Leaving directory '/home/benjamin/MY_APPS/my-first-react-app/node_modules/fsevents/build'
node-pre-gyp info ok 
npm notice created a lockfile as package-lock.json. You should commit this file.
+ [email protected]
+ [email protected]
+ [email protected]
added 1193 packages in 31.426s
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).
There are known issues with Node 8 at the moment that are fixed in master. Please downgrade to Node 7 and wait until the next release.
Thanks for the update. :)
FWIW Node 8 should work with latest version. But you still need to downgrade npm to 4.x because 5.x is too buggy right now.
I have node 7.9.x and npm 4.6.x still have the same issue?
Thank you, my issue is completed! :)
@JuLiAnChz how you complete your issue? please give a solution
Most helpful comment
FWIW Node 8 should work with latest version. But you still need to downgrade npm to 4.x because 5.x is too buggy right now.