@alexander-akait I know that you have closed all the issue requesting this change by saying that it is a "breaking change". While I do understand the reasoning behind this, it is worth considering that versions older than node 8 (the earliest release supported by chokidar v3) have been out of LTS for years now. There is no obligation to continue to support these versions. Not to mention that chokidar v2 will cease to work versions of node 14+ (the current LTS). Should support for those versions not be more important?

I know that the release of v4, which does include this upgrade, is imminent. Most of the time this repo is downloaded as a sub-dependency of something else. This implies that all projects will have to upgrade their dependency on webpack-dev-server before this issue can be called fixed. I don't know what changes are planned for v4, but I'm assuming that, since it is a "major" version change, they will require some work to integrate with.

Also consider that chokidar v2 does not have support for the new Apple M1 chips. I'm not using one, but apple products are extremely common among the node/js community.

I'm sure that I'm not alone in saying that making this upgrade would save a lot of trouble for a lot of people. I would ask you to please reconsider your stance on this issue or at least give us solid reasoning on why this change will not be made.