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

fsevents Catalina v.10.15.4 and node v13.11.0 #315

Closed
snamstorm opened this issue Apr 8, 2020 · 3 comments
Closed

fsevents Catalina v.10.15.4 and node v13.11.0 #315

snamstorm opened this issue Apr 8, 2020 · 3 comments

Comments

@snamstorm
Copy link

Just setup an existing project on a new machine running OS Catalina v.10.15.4

node version: v13.11.0
npm version: 6.13.7

Getting the below errors when doing npm install

> node install

node-pre-gyp WARN Using request for node-pre-gyp https download 
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.9/fse-v1.2.9-node-v79-darwin-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.9 and node@13.11.0 (node-v79 ABI, unknown) (falling back to source compile with node-gyp) 

I get many errors further down the log like this also

> 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-v79-darwin-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.4 and node@13.11.0 (node-v79 ABI, unknown) (falling back to source compile with node-gyp) 
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:221:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:22:1: error: no viable conversion from 'Local<v8::Context>' to 'v8::Isolate *'
X(Boolean)

I have probably missed something but can't seem to see what the issue is - appreciate any help.

Thanks!

@high-performance-hery
Copy link

Are you using react-scripts? I had that same issue and fixed it by updating to the latest version of react-scripts. If not, try updating whichever lib is refering to that old version?

@jason-hwang
Copy link

jason-hwang commented May 3, 2020

same with me. I am using react-script-ts

@paulmillr
Copy link
Member

React-scripts is using webpack. Webpack didn't upgrade fsevents. Ask webpack to release new version with chokidar 3 & fsevents 2. Leave a comment here.

webpack/watchpack#153
webpack/webpack-dev-server#2539

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