add a prefix to the path that sockjs-node is mounted to

[kellyrmilligan]

Do you want to request a feature or report a bug?

What is the current behavior?

Currently, the path is always /sockjs-node.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

If this is a feature request, what is motivation or use case for changing the behavior?
The request would be to be able to be able to add a prefix to this path, in order to be able to have multiple apps running with webpack dev server in a reverse proxy scenario, in order to fully isolate an app running under a sub path.

see:
facebook/create-react-app#1887
and
facebook/create-react-app#1582

Proposal would be to add a configuration option to mount the sockjs handler to the express instance at a prefixed-path. this implies that the provided webpack dev client would also be able to access this same path so that they are in sync.

thoughts?
Please mention your webpack and Operating System version.

[kellyrmilligan]

update, how about prefixing it with options.publicPath ?

[kellyrmilligan]

is there any way to access the webpack config from within the client/index.js file? any variables injected when webpack is compiling it?

[shellscape]

Closing this as the resolution to #1021 will resolve it.