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 1 might no longer work on Node 14+ #8278

Closed
Artur- opened this issue May 8, 2020 · 3 comments · Fixed by #8473
Closed

Fsevents 1 might no longer work on Node 14+ #8278

Artur- opened this issue May 8, 2020 · 3 comments · Fixed by #8473

Comments

@Artur-
Copy link
Member

Artur- commented May 8, 2020

npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
@Artur-
Copy link
Member Author

Artur- commented May 8, 2020

fsevents 1 is included through chokidar 2

chokidar 2 is included through:

  1. [email protected] through [email protected] (Fix pending in Update chokidar to 3.3.0 webpack/watchpack#153)
  2. [email protected] through @babel/cli@7 (Please update chokidar optional dependency to 3.4.0 from 2.1.8 for @babel/cli package babel/babel#11488 (comment) says it will not be fixed before @babel/cli version 8 at some point but that a new version can be forced)
  3. [email protected] (Fixed in chore(deps): upgrade chokidar webpack/webpack-dev-server#2539, pending release)

@Artur-
Copy link
Member Author

Artur- commented May 12, 2020

https://github.com/fsevents/fsevents/releases/tag/v2.0.0

We have upgraded to N-API. For that reason we have also dropped support for node < 6.

For that reason, we have made this a major version bump so dependents have to opt in. The actual API remains entirely the same, so if you are depending on fsevents, it should be as simple as changing the version number in your package.json.

@mocca-dev
Copy link

I'm having the same issue

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

Successfully merging a pull request may close this issue.

3 participants