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

Bugfix for webpack-dev-server 3.1.11 #1795

Merged
merged 2 commits into from
May 13, 2019
Merged

Conversation

jlieb10
Copy link
Contributor

@jlieb10 jlieb10 commented May 13, 2019

Upgrading webpack-dev-server to 3.1.11 causes constant console logging due to new security features. The current best supported work around is to add the --disable-host-check flag to the
script in package.json

Please see webpack-dev-server's documentation of this issue here

TBD: check to see if this flag is still necessary next time we upgrade webpack-dev-server

…roduced changes that cause constant console logging running locally
@jlieb10 jlieb10 requested a review from a team May 13, 2019 15:12
@@ -11,7 +11,7 @@
"build-ssr": "webpack --config webpack.ssr.js && node scripts/ssrScript.js",
"build-prod": "npm-run-all clean validate test storybook-static 'webpack --config webpack.prod.js --env.prod'",
"webpack": "webpack",
"webpack-dev-server": "webpack-dev-server --config webpack.dev.js --port 9211 --public support.thegulocal.com",
"webpack-dev-server": "webpack-dev-server --config webpack.dev.js --port 9211 --public support.thegulocal.com --disable-host-check",
Copy link
Member

Choose a reason for hiding this comment

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

is it possible to add a comment with a link to the issue jonny was looking at?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@johnduffell comments are not supported in json files so we settled for a PR with the documentation 😢

@johnduffell
Copy link
Member

good, but see my comment. although it can be linked back to the PR, it might be nice to comment inline so it is more obvious.
Also, Rupert is looking at the master build failure.
👍 other than that thanks!

@jlieb10
Copy link
Contributor Author

jlieb10 commented May 13, 2019

@johnduffell your PR was definitely not the source of the issue - you just brought the yarn.lock file up to date with the packages that we are currently using, which should've happened when the last package was updated

Also, unfortunately inline comments are not supported in json files

@jlieb10
Copy link
Contributor Author

jlieb10 commented May 13, 2019

Related PR: #1774

@jlieb10 jlieb10 merged commit cd14098 into master May 13, 2019
@jlieb10 jlieb10 deleted the jtl-webpack-dev-server-bugfix branch May 13, 2019 15:43
@prout-bot
Copy link

✅ Testing in PROD passed! Details

@prout-bot
Copy link

Seen on PROD (merged by @jlieb10 13 minutes ago)

Sentry Release: support-client-side, support

@prout-bot
Copy link

✅ Testing in PROD passed! Details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants