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
Hot Module Reload may not work when running yarn serve from a docker container, or when accessing to the dev server from a NAT network that may have a different IP / Port than the configured one inside vue.config.js.
Problem is that client may fail to connect back to the webpack-dev-server because host/port is wrong (webpack/webpack-dev-server#416).
It should be possible to provide options to provide the host/port that should be used to reach the webpack-dev-server from the browser. Those options should be passed to create the right entry point for webpack-dev-server client
What does the proposed API look like?
module.exports={devServer: {host: '0.0.0.0',port: 1288,public: {// To be used by the browserhost: '192.168.1.100',port: 80,},disableHostCheck: true}}
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
Hot Module Reload may not work when running
yarn serve
from a docker container, or when accessing to the dev server from a NAT network that may have a different IP / Port than the configured one insidevue.config.js
.Problem is that client may fail to connect back to the webpack-dev-server because
host
/port
is wrong (webpack/webpack-dev-server#416).It should be possible to provide options to provide the
host
/port
that should be used to reach the webpack-dev-server from the browser. Those options should be passed to create the right entry point for webpack-dev-server clientWhat does the proposed API look like?
The text was updated successfully, but these errors were encountered: