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

npm install error when trying to install fsevents #252

Closed
oveddan opened this issue Dec 30, 2018 · 3 comments
Closed

npm install error when trying to install fsevents #252

oveddan opened this issue Dec 30, 2018 · 3 comments

Comments

@oveddan
Copy link
Contributor

oveddan commented Dec 30, 2018

When running npm install, I get the error:

npm install

fsevents@1.2.4 install /Users/danoved/Source/ml5-library/node_modules/fsevents
node install

node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v67-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.4 and node@11.0.0 (node-v67 ABI, unknown) (falling back to source compile with node-gyp)
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Darwin 18.0.0
gyp ERR! command "/usr/local/Cellar/node/10.12.0/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/Users/danoved/Source/ml5-library/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/danoved/Source/ml5-library/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /Users/danoved/Source/ml5-library/node_modules/fsevents
gyp ERR! node -v v11.0.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

With a bunch more after that. I'm still able to run npm run start

I've traced fsevents and its needed by chokidar, which is needed by webpack-dev-server.

@meiamsome
Copy link
Contributor

meiamsome commented Dec 30, 2018

fsevents is optional for chockidar, and so this doesn't actually cause any install failure - the error message provider simply says that if you want fsevents features (I believe this is used for watching the file system on Macs) you should either use an older node version that has a pre built binary, wait for a binary for 11.0.0 to be released or install Xcode so that fsevents can be built from source. This is not an ml5 error itself.

There's an open ticket for prebuilt 11.x versions of fsevents: fsevents/fsevents#244

However, looks like as of version 2 of fsevents, binary building is no longer required, so another solution is to wait for that version to trickle up the dependency tree (chokidar needs to update to that version of fsevents then webpack-dev-server needs to update to that version of chockidar then ml5 needs to update to that version of webpack-dev-server.) But as this is just a very specific node version failure, I'm not sure it's worth having an open issue here for it at the moment. Perhaps it would be good to open ones upstream, though, for chockidar specifically, I guess.

@cvalenzuela
Copy link
Member

Thanks for the detailed response @meiamsome. Since this is not a ml5 specific issue I'll close it. @oveddan, feel free to open it again if you feel there's something else.

@Parthan-Akon
Copy link

I also had the same issue though am using MacOS the issue is kind of bug. I solved this issue by repeatedly running the commands,

  • sudo npm cache clean --force
  • sudo npm uninstall
  • sudo npm install

One time it did not worked but when I repeatedly cleaned the cache and after uninstalling npm, reinstalled npm, the error went off. Am using Angular 8 and this issue is common

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants