-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request to extend use of sockjs #1661
Comments
What is real use case? Why you need send messages? Please provide PoC |
My initial use case is that be able to serialize key events on my browser to send to each device and then unserialize the key event on each device to simulate the key event on the device. This feature will only be in development to speed up testing. Webpack and Webpack dev server has been a great tool for me when working cross platform and multiple devices. Also has some other ideas to be able to send logs/errors to webpack dev server because some devices has really shitty development tools. So I can output that data in my laptop console. I think there could be multiple new features with this. |
@EloB hm, PR welcome 👍 |
Close in favor #1860, will be implemented for next major release, thanks for issue |
As workaround right now you can use own client (or extend our) |
I would like a simple way to communicate between clients and devServer.
By using the
devServer.before
property. We could do something like:In the code I see that we expose message sent.
https://github.com/webpack/webpack-dev-server/blob/master/client-src/default/index.js#L71
If we could add
custom
to https://github.com/webpack/webpack-dev-server/blob/master/client-src/default/index.js#L81Like this:
Why add this?
In my case I use multi compiler (multiple configs) because I develop to multiple devices. What I'm trying to achieve is development tools when I run
webpack-dev-server
.This is how my webpack.config.babel.js looks like
So when I visit for instance
http://localhost/
when runningwebpack-dev-server
I see some devtools. I would imagine./src/devtools
to look something like this.The question you might be thinking of is why not add this as a separate solution? It's because of the hassle of trying to figure out where the webpack-dev-server is located on the network. You guys already do that (see link below). Then we can extend webpack-dev-server with even more cool tools/plugins :)
https://github.com/webpack/webpack-dev-server/blob/master/client-src/default/index.js#L34
The text was updated successfully, but these errors were encountered: