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 Oct 2, 2019. It is now read-only.
Then the hard-coded localhost is a bit misleading. Since webpack-dev-server already prints the host and port binding on the line immediately prior, it might make sense to just limit the publicPath setting to the actual file path (/webpack). For example:
http://10.0.0.100:3808/webpack-dev-server/
webpack result is served from /webpack/
In reading the webpack-dev-server documentation, it looks like publicPath is supposed to be relative, but I'm still learning, so I'm not sure, but it works for me with just the relative path setting.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This isn't necessarily a bug, but it's potentially confusing. When you start the server with the default
config/webpack.config.js
, it prints:While this is true in the default case, if you start it with a custom host binding, like this:
Then the hard-coded
localhost
is a bit misleading. Since webpack-dev-server already prints the host and port binding on the line immediately prior, it might make sense to just limit thepublicPath
setting to the actual file path (/webpack
). For example:In reading the webpack-dev-server documentation, it looks like
publicPath
is supposed to be relative, but I'm still learning, so I'm not sure, but it works for me with just the relative path setting.The text was updated successfully, but these errors were encountered: