Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node-pre-gyp error but app still functioning

See original GitHub issue

Software OSX 10.13.1 node: 9.2.0 npm: 5.5.1

Questions:

Does node-pre-gyp server down? If it does. How can I fix my error?
Do I need to install XCode? I am now working on ReactJS not ReactNative

Thanks

Creating a new React app in /Users/sarit/study/egghead.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...


> fsevents@1.1.2 install /Users/sarit/study/egghead/node_modules/fsevents
> node install

node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.2/fse-v1.1.2-node-v59-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.2 and node@9.2.0 (node-v59 ABI) (falling back to source compile with node-gyp)
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  COPY /Users/sarit/study/egghead/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp

> uglifyjs-webpack-plugin@0.4.6 postinstall /Users/sarit/study/egghead/node_modules/uglifyjs-webpack-plugin
> node lib/post_install.js

+ react@16.2.0
+ react-dom@16.2.0
+ react-scripts@1.0.17
added 1266 packages in 61.113s

Success! Created egghead at /Users/sarit/study/egghead
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 egghead
  npm start

Happy hacking!

Issue Analytics

State:
Created 6 years ago
Reactions:3
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

gaearoncommented, Feb 9, 2018

You can’t have several versions at the same time if you install it globally (as with Homebrew).

0reactions

ghostcommented, Nov 23, 2018

What is the exact node version, as per docs here, it says Node 8. So does that mean I can use v8.13.0 or it has to be v8.0.0?

Thanks

Top Results From Across the Web

node.js - Error with npm install - a pre-gyp error - Stack Overflow

I faced this error when I was running a project which has sqlite3 package and It seems like the one causing error when...

Solving common issues with node-gyp - LogRocket Blog

Many node-gyp issues are actually issues with the toolchain used for building add-on code. We'll categorize these issues to offer solutions.

A Comprehensive Guide to Fixing Node-Gyp Issues on Windows

1. Try running npm install with the --no-optional flag. · 2. Try downloading the windows-build-tools package. · 3. Download the Visual Studio 2015 ......

Problems with npm install after loading project files. - Treehouse

Pre -built binaries not found for fsevents@1.0.14 and node@10.13.0 (node-v64 ... _handle.onexit (internal/child_process.js:240:12) gyp ERR!

node-gyp - npm

Node.js native addon build tool. Latest version: 9.3.1, last published: 8 days ago. Start using node-gyp in your project by running `npm i ......