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

need to update to newer FSEvents for MacOS 15 #131

Closed
mattbishop opened this issue Nov 4, 2019 · 5 comments
Closed

need to update to newer FSEvents for MacOS 15 #131

mattbishop opened this issue Nov 4, 2019 · 5 comments

Comments

@mattbishop
Copy link

This is for version 1.6.0.
Might be a duplicate for #122

@alexander-akait
Copy link
Member

What is problem?

@mattbishop
Copy link
Author

mattbishop commented Nov 5, 2019

I can't install webpack because watchpack failed to build due to fsevents on MacOS 15. Below is a log output:

[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
warning Error running install script for optional dependency: "/Users/matt/Projects/Identifiers/identifiers-js/node_modules/fsevents: Command failed.
...
yarn why v1.19.1
[1/4] 🤔  Why do we have the module "fsevents"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "fsevents@1.2.4"
info Reasons this module exists
   - "webpack#watchpack#chokidar" depends on it
   - Hoisted from "webpack#watchpack#chokidar#fsevents"

This is an fsevents bug, fixed in version 1.2.9: fsevents/fsevents#274

So, please update watch pack to fsevents 1.2.9.

Thanks!

@alexander-akait
Copy link
Member

Just update own deps/lock file

@mattbishop
Copy link
Author

Yes, but I was filing this so you can help your other users avoid this in the future. Being part of a well-used project like webpack has some heightened responsibilities, like keeping your dependencies up-to-date.

@alexander-akait
Copy link
Member

@mattbishop so we use ^ for packages in package.json, each fresh installation will get new versions, we don't want do release on each patch version of dependencies and transitive dependencies, so update you lock file, you can setup renovate or other dependencies bots to keep lock file up to date

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

2 participants