Glen Mailer

I agree I'd like to have it standalone and pull it in. It would be nicer to be outside dev-utils but I don't think that's a huge issue as this...

This code appears correct, but could you describe a use-case which would motivate doing this?

I'd take a PR which adds this capability - what scenarios do you need this for? Is it just to provide a way to cleanly shutdown?

Ok, it should be a case of going through the open sockets for the server-sent-events connections and disconnecting them.

The default browser limits vary depending on the transport used. Can I ask why you need to have so many active tabs open during development? There are some possible strategies...

Also, webpack-hot-middleware is designed to seamlessly combine with an existing server. Because websocket events are global on an express server instance, it is not possible to use web sockets and...

Ok, that makes sense - it is relatively unusual to need to have lots of tabs open in the same browser and an SSE connection open for each one -...

The SSE approach is a bit limiting, but most users don’t run into these limits. There is some discussion from the early days in https://github.com/webpack-contrib/webpack-hot-middleware/issues/121 The goal of this module...

I have never really used multi compiler setups, so don’t have much to add here. But Multi-compiler support in webpack is using one compiler instance with multiple configs passed to...

You can set the `path` option on client and server to do exactly that