You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 8, 2019. It is now read-only.
When i create const socket = new WebSocket('ws://localhost:8090'); (hardcode host and port) and using auto search available port (i.e. don't use port in settings) it is impossible get resolved port for socket server.
If second argument will be passed i can do like this:
This issue is for a:
Code
CLI Command
$ webpack-serve
webpack.config.js
From https://github.com/webpack-contrib/webpack-serve/blob/master/docs/addons/watch-content.config.js
Expected Behavior
Second arguments in
listening
event should beoptions
Actual Behavior
Second argument is undefined. Impossible run multiple instances without hack and workaround for watching content
How Do We Reproduce?
Use this repo https://github.com/webpack-contrib/webpack-serve/blob/master/docs/addons/watch-content.config.js (remove
hot.port
) and run multiple instances.New Feature Use Case
Why?
When i create
const socket = new WebSocket('ws://localhost:8090');
(hardcode host and port) and using auto search available port (i.e. don't use port in settings) it is impossible get resolved port for socket server.If second argument will be passed i can do like this:
The text was updated successfully, but these errors were encountered: