Skip to content
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

Upgrade webpack-dev-server and fix public path which is now validated… #635

Merged
merged 1 commit into from
Jun 2, 2017

Conversation

OzzieOrca
Copy link
Contributor

… in 2.4.3

Bill ran into this I'm assuming because he used npm and npm ignores the yarn lock file and grabbed the newest version of webpack-dev-server for him. localhost.cru.org was giving a Invalid Host header error.

https://github.com/webpack/webpack-dev-server/releases/tag/v2.4.3

webpack/webpack-dev-server#882

@@ -137,7 +137,8 @@ module.exports = env => {
'/etc': aemDomain,
'/designations': aemDomain
},
port: 9000
port: 9000,
public: "localhost.cru.org:9000"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the value for localhost, but wouldn't be for other environments. Not sure if that matters.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This dev server is only for development. S3 serves the js everywhere else. This should be good.

@OzzieOrca OzzieOrca merged commit a785353 into master Jun 2, 2017
@OzzieOrca OzzieOrca deleted the upgrade-webpack-dev-server branch June 2, 2017 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants