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.

Sign up for GitHub

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

Jump to bottom

[critical] regression in findPort after refactor #1991

Closed
1 of 2 tasks
alexander-akait opened this issue Jun 7, 2019 · 0 comments · Fixed by #1993
Closed
1 of 2 tasks

[critical] regression in findPort after refactor #1991

alexander-akait opened this issue Jun 7, 2019 · 0 comments · Fixed by #1993
Labels
priority: 1 (critical) scope: server severity: 2 (regression) type: bug

Comments

@alexander-akait
Copy link
Member

alexander-akait commented Jun 7, 2019 •
edited

  • Operating System: -
  • Node Version: -
  • NPM Version: -
  • webpack Version: -
  • webpack-dev-server Version: 3.7.0
  • This is a bug
  • This is a modification request

Code

After refactor findPort behavior was changed

Expected Behavior

Ports must be taken consistently.

Actual Behavior

Ports get randomly.

For Bugs; How can we reproduce the behavior?

Just try to run webpack-dev-server on 8080 port where they busy

For Features; What is the motivation and/or use-case for the feature?

no
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: 1 (critical) scope: server severity: 2 (regression) type: bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: retry finding port when port is null and get ports in sequence webpack/webpack-dev-server
1 participant
@alexander-akait