Update Chokidar to v3 for [email protected]

[guidobouman]

[email protected] causes [email protected] + [email protected] to be installed. Which breaks on Windows with npm ci installs.

Using [email protected] in the v1.x branch allows [email protected] to be installed, which allows ci installs on Windows to succeed again. With every package update, I now have to manually roll back the fsevents update. Yes, I've brought this up with the package owner, but he's also in a position where [email protected] is unmaintainable. This package would benefit a lot from the update in the current v1.x branch. Because current installs of webpack / watchpack are starting to fail more & more.

[alexander-akait]

We can't do it because it is breaking change, what is broken? Can you create reproducible test repo?

[guidobouman]

Would that directly cause a breaking change in the watchpack API? I don't see the need for a breaking change in watchpack to update a dependency. Or do I see this wrong?

[alexander-akait]

@guidobouman webpack@4 support node@6, [email protected] require node@8

[guidobouman]

Hmm... You mean Node 6, which has been EOL since april 30, 2019? I get that you want to respect old versions, even if they are EOL. But should a widespread package like webpack not also push ahead the platform as a whole?

Google is decommissioning Node 6 cloud functions on April 22, 2020. And Amazon has deprecated Node 6 for Lambda functions on August 12, 2019:
https://aws.amazon.com/blogs/developer/node-js-6-is-approaching-end-of-life-upgrade-your-aws-lambda-functions-to-the-node-js-10-lts/

[alexander-akait]

@guidobouman yes, but it will be in webpack@5 (we don't use chokidar in next version), we can't break support for node@6 projects

[guidobouman]

Fair point. Sorry for pushing beyond reasonable semver logic.