Install failing on optional dependency fsevents@1.2.7 in @babel/cli
See original GitHub issueBug Report
Apparently fsevents@1.2.7
can’t be installed because the binary is no longer available due to that it’s deprecated (security risk):
https://github.com/fsevents/fsevents/issues/341
Running yarn why fsevents
yeilds:
=> Found "fsevents@1.2.7"
info Has been hoisted to "fsevents"
info Reasons this module exists
- Hoisted from "chokidar#fsevents"
- Hoisted from "@babel#cli#@nicolo-ribaudo#chokidar-2#chokidar#fsevents"
Error log
arning Error running install script for optional dependency: "/Users/kenny/Documents/hero/payments/node_modules/fsevents: Command failed.
Exit code: 1
Command: node install
Arguments:
Directory: /Users/kenny/Documents/hero/payments/node_modules/fsevents
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using node-pre-gyp@0.10.3
node-pre-gyp info using node@12.18.4 | darwin | x64
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp info check checked for \"/Users/kenny/Documents/hero/payments/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node\" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.7 and node@12.18.4 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not installable for fsevents@1.2.7 and node@12.18.4 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error Connection closed while downloading tarball file
Environment
System:
OS: macOS 10.15.7
Binaries:
Node: 12.18.4 - ~/.nvm/versions/node/v12.18.4/bin/node
Yarn: 1.22.4 - ~/.nvm/versions/node/v12.18.4/bin/yarn
npm: 6.5.0 - ~/Documents/some/path/node_modules/.bin/npm
npmPackages:
@babel/cli: 7.12.1 => 7.12.1
@babel/core: ^7.2.2 => 7.3.3
@babel/preset-env: ^7.3.1 => 7.3.1
@babel/preset-react: ^7.0.0 => 7.0.0
babel-eslint: ^10.0.1 => 10.0.1
babel-jest: ^24.0.0 => 24.1.0
eslint: ^5.14.1 => 5.14.1
jest: ^24.0.0 => 24.1.0
rollup-plugin-babel: ^4.3.2 => 4.3.2
Possible Solution
Update @nicolo-ribaudo/chokidar-2
in @babel/cli
Thanks in advance 😃
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to solve npm install throwing fsevents warning on non ...
As the above error message states that fsevents is optional and it is ... you just need to install fsevents as a optional...
Read more >【NPM】cnpm无法打包问题解决_wx630390aa6b966的技术博客_ ...
[13/26] Installing @babel/core@^7.11.0platform unsupported ... [fsevents@^1.2.7] optional install error: Package require os(darwin) not compatible with your ...
Read more >error found incompatible module. - You.com | The AI Search ...
info fsevents@2.0.7: The platform "linux" is incompatible with this module. info "fsevents@2.0.7" is an optional dependency and failed compatibility check.
Read more >Error Installing Discovery CLI - Secret Nodes
I get this permissions error when installing the Discovery CLI ... npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 ...
Read more >How to fix Error from chokidar (C:\): Error: EBUSY while installing a ...
... commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules\@babel\cli\node_modules\chokidar\node_modules\fsevents): ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Btw, in the next patch release the warning should go away.
I have a fix that should make the warning go away and still work on Node.js 6, but I’ll need someone with MacOS to confirm that it works (I’ll open a PR soon).