-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
configuration has an unknown property 'allowedHosts' #944
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
Comments
Is there any workaround available for this? Just ran headlong into it. Kind of a bummer. |
@dfcowell Are you using WDS 2.5.0? |
Hmm, looks like something in my config doesn't play nicely with 2.5.0. Probably unrelated. My 2.4.5 config worked fine though (apart from the issue with allowedHosts of course). I'll have a poke around and see if I can identify the issue. If I get 2.5.0 working I'll report back with the result.
|
Yeah, I haven't seen that one before. It could be a bug somewhere but without a standalone project it's hard to tell. |
This one was resolved with #1012 and is available in the latest version. |
Do you want to request a feature or report a bug?
Bug 🐛
What is the current behavior?
I added devServer.allowedHosts to my
webpack.config.js
and it complains withIf the current behavior is a bug, please provide the steps to reproduce.
Just add
to your
webpack.config.js
What is the expected behavior?
It should not complain about it because the property is documented here
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
webpack
2.6.1
I just want to access the
webpack-dev-server
outside of my local dev machine (e.g. my mobile phone)This issue was moved from webpack/webpack#5080 by @bebraw. Orginal issue was by @screendriver.
The text was updated successfully, but these errors were encountered: