Fsevents: latest fsevent binary file and source archive are missed from s3
Here's what I tried to run npm install on ubuntu 16.04.
node-pre-gyp info check checked for "/opt/homepage/node_modules/fsevents/lib/binding/Release/node-v48-linux-x64/fse.node" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-linux-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-linux-x64.tar.gz
node-pre-gyp ERR! Tried to download: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v48 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http Pre-built binary not available for your system, looked for https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-linux-x64.tar.gz
gyp info it worked if it ends with ok
Seems like it's true
~> curl -I https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.14/fse-v1.0.14-node-v48-linux-x64.tar.gz
HTTP/1.1 404 Not Found
x-amz-request-id: 41D00694186891E7
x-amz-id-2: SDIGlsuGfLxBhHlHCE03HJ1v5gPTX/ELTzB3y1gpPXK2Xvo+ydgaGeewidZooc/bNhvlYAEZfGE=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Fri, 05 Aug 2016 01:44:22 GMT
Server: AmazonS3
Can anyone help fix this? It's ok under osx, but we need to run it on CI agent.
iambowen
All 3 comments
There is no linux binary because it's an OS X-only module. Add it to your optionalDependencies. Good luck.
bnoordhuis
on 5 Aug 2016
You're probably using a shrinkwrap file generated on OS X. npm doesn't handle this well (https://github.com/npm/npm/issues/2679), so you need to adjust your shrinkwrap workflow to prevent os x-specific dependencies from getting in there, such as generating it only on Linux machines or running rm -rf node_modules && npm install --no-optional prior to generating the shrinkwrap file.
es128
on 5 Aug 2016
thanks @es128 pulled updates from macOS to Linux and problems started. Your comment lead me to the solution
OmarBizreh
on 20 Jun 2017
Related issues
kroschu
路
7Comments
pddkhanh
路
6Comments
noelheesen
路
6Comments
thinkingdyw
路
5Comments
zsociety
路
6Comments
Most helpful comment
You're probably using a shrinkwrap file generated on OS X. npm doesn't handle this well (https://github.com/npm/npm/issues/2679), so you need to adjust your shrinkwrap workflow to prevent os x-specific dependencies from getting in there, such as generating it only on Linux machines or running
rm -rf node_modules && npm install --no-optionalprior to generating the shrinkwrap file.