Glen Mailer

Can you try logging out ``` js process._getActiveHandles() // and process._getActiveRequests() ``` At the point when you think the process should be shutting down cleanly?

I haven’t had a chance to try it out yet. Are there any issues?

Looks like there is a guide here: https://medium.com/webpack/webpack-4-migration-guide-for-plugins-loaders-20a79b927202 Haven’t read it yet, but I want to maintain compatibility with 4 at the same time.

Looks good, will aim to update later today, unless someone beats me to it with a PR

I've just pushed ae79f6a to `master` which I've released as `v2.21.1` onto npm. This supports the old plugin API as well as the new one. While testing this I seem...

Oh, and you will still see a warning from `webpack-dev-middleware` until that gets upgraded. Slightly annoyingly they've decided to go to v3 for the fix and break back-compat with older...

If you use `webpack --watch` to do the building & rebuilding are the times the same? What about if you comment out the references to `webpack-hot-middleware`? If you still see...

The deprecation warning on that `npm` package is actively harmful imo. > The querystring API is considered Legacy. While it is still maintained, new code should use the API instead....

> using standard APIs for such a minor usecase would offer better long term support. Yeah, if this was a random 3rd party module I'd be more inclined to switch,...

The only barrier right now is that I never got around to it, and I really really really dislike that they've marked a core library as actively deprecated rather than...