Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-pre-gyp error but app still functioning #3588

Closed
elcolie opened this issue Dec 13, 2017 · 8 comments
Closed

node-pre-gyp error but app still functioning #3588

elcolie opened this issue Dec 13, 2017 · 8 comments

Comments

@elcolie
Copy link

elcolie commented Dec 13, 2017

Software
OSX 10.13.1
node: 9.2.0
npm: 5.5.1

Questions:

  1. Does node-pre-gyp server down?
    If it does. How can I fix my error?
  2. 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!
@hamaney
Copy link

hamaney commented Dec 22, 2017

Same issue i have

@Timer
Copy link
Contributor

Timer commented Dec 29, 2017

Many things aren't precompiled for Node 9 yet, you should be using Node 8.

This error is caused by a misconfigured development environment [when your machine tries to build the missing binary] -- see nodejs/node-gyp#569 on how to fix.

@Timer Timer closed this as completed Dec 29, 2017
@elcolie
Copy link
Author

elcolie commented Dec 30, 2017

@Timer Thank you. Node 8 builds without any error 👍

@hamaney
Copy link

hamaney commented Jan 3, 2018

so are u suggesting for now to:
brew uninstall node then brew install node@8 ? just making sure

@Timer
Copy link
Contributor

Timer commented Jan 3, 2018

I wouldn't suggest using Homebrew to install Node. I personally use n.

@raarts
Copy link

raarts commented Feb 9, 2018

@Timer why? Can you explain what's wrong with homebrew install?

@gaearon
Copy link
Contributor

gaearon commented Feb 9, 2018

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

@ghost
Copy link

ghost commented 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

@lock lock bot locked and limited conversation to collaborators Jan 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants