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

[regression] clientLogLevel should alias options "none" and "warning" #1899

Closed
hubgit opened this issue May 17, 2019 · 0 comments · Fixed by #1901
Closed

[regression] clientLogLevel should alias options "none" and "warning" #1899

hubgit opened this issue May 17, 2019 · 0 comments · Fixed by #1901
Labels
priority: 2 (urgent) semver: patch severity: 2 (regression) type: bug
Milestone
3.4.1

Comments

@hubgit
Copy link

hubgit commented May 17, 2019

#1825 removed the clientLogLevel options "none" and "warning".

This is causing an error when a project tries to run webpack-dev-server with a previously valid clientLogLevel value .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: 2 (urgent) semver: patch severity: 2 (regression) type: bug
Projects
None yet
Milestone
3.4.1
Development

Successfully merging a pull request may close this issue.

fix: add none and warning to clientLogLevel webpack/webpack-dev-server
2 participants
@hubgit @alexander-akait