fsevents: Install on OS X fails as prebuilt binary seems to be missing from S3
Install Fails
When we run yarn install we’re getting the following:
$ yarn install
yarn install v0.27.5
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/1] ⠂ fsevents: node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz
[-/1] ⠂ waiting...
[-/1] ⠂ waiting...
[-/1] ⠂ waiting...
warning Error running install script for optional dependency: "/Users/danieldbird/Code/toolkit-for-ynab/node_modules/fsevents: Command failed.\nExit code: 1\nCommand: sh\nArguments: -c node install\nDirectory: /Us
ers/danieldbird/Code/toolkit-for-ynab/node_modules/fsevents\nOutput:\nnode-pre-gyp info it worked if it ends with ok\nnode-pre-gyp info using node-pre-gyp@0.6.33\nnode-pre-gyp info using node@8.1.3 | darwin | x64\
nnode-pre-gyp info check checked for \"/Users/danieldbird/Code/toolkit-for-ynab/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node\" (not found)\nnode-pre-gyp http GET https://fsevents-binaries
.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz\nnode-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz\nnode-pre-gyp ERR!
Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz \nnode-pre-gyp ERR! Pre-built binaries not found for fsevents@1.1.1 and node@8.1.3 (node-v5
7 ABI) (falling back to source compile with node-gyp) \nnode-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz \nnod
e-pre-gyp ERR! build error \nnode-pre-gyp ERR! stack Error: Failed to execute 'node-gyp clean' (Error: spawn node-gyp ENOENT)\nnode-pre-gyp ERR! stack at ChildProcess.<anonymous> (/Users/danieldbird/Code/toolk
it-for-ynab/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:77:29)\nnode-pre-gyp ERR! stack at emitOne (events.js:115:13)\nnode-pre-gyp ERR! stack at ChildProcess.emit (events.js:210:7)
\nnode-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:195:12)\nnode-pre-gyp ERR! stack at onErrorNT (internal/child_process.js:366:16)\nnode-pre-gyp ERR! stack at
_combinedTickCallback (internal/process/next_tick.js:102:11)\nnode-pre-gyp ERR! stack at process._tickCallback (internal/process/next_tick.js:161:9)\nnode-pre-gyp ERR! System Darwin 16.6.0\nnode-pre-gyp ERR! c
Done in 4.08s.
You can replicate by cloning the repo here: https://github.com/toolkit-for-ynab/toolkit-for-ynab then running yarn.
Analysis
It looks to me like this error is because it’s trying to download this tarball: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.1/fse-v1.1.1-node-v57-darwin-x64.tar.gz which 404s on S3.
Is there a way to work around this?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 14
- Comments: 15 (4 by maintainers)
I solved this issue by update to lastest version of fsevents.
npm install fsevents@latestnpm install -D fsevents@1.2.4resolved the issue on node10.8.0.can confirm installing fsevents v1.2.4 solved this issue on node 10.5.0
If you’re on node v10, then you need fsevents v1.2.3 minimum
npm install fsevents@latest worked. Thanks
Similar to @pesterhazy, I resolved the issue on my system by downgrading to the current LTS version of Node, which happens to be version
8.11.2at the moment. Before this I was on version10.2.1.It could be a yarn issue, true. Thanks for your help. I fixed this by downgrading to node 6 (
brew install node@6)The same as @jayantbh. I have to downgrade node from
8.11to10.2.1. And I fix the problem@pesterhazy try running
yarn cache cleanI’m seeing the same error. But I added
1.1.2and it’s right there in yarn.lock. fsevents still tries to grab the 1.1.1 url from s3.It’s not an fsevents issue. You could try deleting and reinstalling all dependencies. If you continue to have issues it sounds like something you should take up with yarn support.
Tks saved me!