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

fix: upgrade webpack-serve and avoid port conflict #425

Merged
merged 3 commits into from
May 13, 2018

Conversation

meteorlxy
Copy link
Member

@meteorlxy meteorlxy commented May 12, 2018

close #424

related webpack-contrib/webpack-serve#135

Before


before

After


after

@meteorlxy meteorlxy changed the title fix: upgrade webpack-serve and fix a bug temporarily fix: upgrade webpack-serve and avoid port conflict May 13, 2018
package.json Outdated
@@ -95,7 +95,7 @@
"webpack": "^4.8.1",
"webpack-chain": "^4.6.0",
"webpack-merge": "^4.1.2",
"webpack-serve": "^0.3.1",
"webpack-serve": "0.3.2",
Copy link
Member

Choose a reason for hiding this comment

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

Don't forget ^

lib/dev.js Outdated
@@ -107,7 +107,10 @@ module.exports = async function dev (sourceDir, cliOptions = {}) {
compiler,
host,
dev: { logLevel: 'warn' },
hot: { logLevel: 'error' },
hot: {
port: parseInt(port) + 1,
Copy link
Member

Choose a reason for hiding this comment

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

portfinder.getPortPromise will return number, so parseInt is unnecessary here.

@ulivz ulivz added the 0.9.0 label May 13, 2018
@ulivz ulivz merged commit 22ffe52 into vuejs:master May 13, 2018
@ulivz ulivz mentioned this pull request May 13, 2018
@meteorlxy meteorlxy deleted the fix-webpack-serve branch September 25, 2018 15:13
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.

The error message of port in use is not correct. Please check whether it is hard-coded.
2 participants