-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
deps: update chokidar to 3.x #59
Conversation
This introduces a breaking change to our compatibility matrix and requires major bumps throughout the system. Half of that work is already in flight. |
@phated totally understand. In the meantime we are likely going to have to remove gulp for the testing matrix for v14 and v12. The change that landed that broke the test suite is a change to the internals of async_hooks, an unrealted API. Gulp's test suite still seems to pass on 12.x... but for some reason that single change broke the suite on 14. When testing glob-watcher it seems like it has consistenly been broken on 14 with pretty serious abort errors. I'm trying to track down which change on 12.x caused things to start breaking |
@MylesBorins are you sure the async_hooks thing isn't our use of domains? As opposed to this issue. |
I'm a bit confused. Is there a way to see these test runs somewhere? |
@terinjokes to reproduce (on OSX only) $ nvm install 12.18.2
$ git clone https://github.com/gulpjs/glob-watcher.git
$ cd glob-watcher
$ npm install
$ npm test output
For v14.x $ nvm install 14.5.0
$ git clone https://github.com/gulpjs/glob-watcher.git
$ cd glob-watcher
$ npm install
$ npm test output
|
FYI, I'm going to be skipping gulp for CITGM on darwin based hosts until we sort this out (either in core or in gulp). |
Preferring #61 over this one - it looks like there's a bunch wrong with upgrading our deps. |
The current version of chokidar used by this project is broken on
Node.js v12.x and v14.x. Updating this version fixes the problem.
Fixes: #58
Fixes: #55
Fixes: #49