Webpack-dev-server: Update chokidar to v3

[paulmillr]

So the decision to keep chokidar v2 around for another year causes more and more users to have issues. https://github.com/fsevents/fsevents/issues/301 It will keep getting worse.

Chokidar v2 uses fsevents v1, which needs node-gyp, may download shady binaries (I say shady even though i'm the maintainer of fsevents) from AWS, causes people to get crazy because of node-gyp's Python v2 dependency (which would become unsupported for security updates in 3 days); breaks the build from time to time.

I strongly suggest updating to chokidar v3! nodejs v8 will be officially unsupported in a couple days. For those who want to stick around with v8, there's always an option to use older webpack-dev-server.

Benefits of upgrading to chokidar v3 are described in a blog post:

• 4.9x faster installtion time
• 9x less traffic to download the pkg
• 13x less dependencies (15 vs 201)
• 16x smaller node_modules size
• Not needing to build a binary on macos! node's nan api is great and works perfectly here.

The downside is just the fact that it requires node 8.10 or higher — not even v10.x.

[alexander-akait]

Will be done in next, we can't do it right now, because we still support node@6, release next version will be in next year. Don't worry we known what we need update that :smile:

[silverwind]

Any news? I'm personally getting tired of dealing with node-gyp.

[HawkeyePierce89]

because we still support node@6

what about people with Node@13 ?

[HawkeyePierce89]

@silverwind you can instal your dependencies like yarn install --ignore-optional or npm install --no-optional

[HawkeyePierce89]

@silverwind ok, I found how fix this shit (next commands for yarn)

• rm -rf node_modules
• yarn cache clean
• partially change fsevents section in yarn.lock (we should only update fsevents version)OR, if it doesn't help, delete yarn.lock
• yarn install --ignore-optional

[silverwind]

I'd rather wait for the dependency update then try such dangerous workarounds 😉