Websocket URL should not include /sockjs-node in the name

[SpaceK33z]

The current websocket URL is /sockjs-node. This is weird, because the websocket library should be completely abstracted from the user. This has some advantages:

• Allows us to switch to another websocket library without a breaking change.
• The URL /sockjs-node might already be in use by the user.
• It makes clear for the user that this websocket connection is from webpack-dev-server (can be confusing in DevTools).
• The current URL is not consistent with the bundles that are currently served, e.g. /__webpack_dev_server__/live.bundle.js.

Note that changing the URL would be a breaking change.

[kellyrmilligan]

related to this, it would be cool to be able to set the handler for sockjs to be under a subpath as well if you have a few sub apps running at the same time. similar to how you can configure the public path to be a subdirectory, historyapifallback can be configured, etc.

[shellscape]

We're going to completely remove SockJS in favor of a native solution for v3, tracking in #1057. While this is still a valid issue, it'll be moot when that work completes, and so, closing.

[ggoodman]

@shellscape I've reviewed #1057 and don't see any mention of adding support for adding a prefix to the websocket path as per #621 (comment).

What would my options be to force the client to look for the socket under a prefix pathname?

[shellscape]

@ggoodman the prefix won't be necessary in v3 because of the complete removal of SockJS in favor of native WebSocket. As of now, there isn't a solution for the 2.x branch. If this is something you're interested in submitting a PR for, we'll welcome and review it.