Skip to content

Make webpack-dev-server npm compatible with [email protected] #962

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

Closed
wants to merge 1 commit into from

Conversation

cchamberlain
Copy link

Currently webpack-dev-server requires webpack@^2.2.0 as a dev / peer dependency. This allows anything greater or equal to 2.2.0 instead.

What kind of change does this PR introduce?
Version fix for npm compatibility.

Did you add or update the examples/?
No, seems unnecessary.

Summary
Currently, npm throws messages about webpack-dev-server not supporting [email protected]. This updates the version range to support webpack 2 or beyond.

Does this PR introduce a breaking change?
To my knowledge, no it does not.

Currently `webpack-dev-server` requires webpack@^2.2.0 as a dev / peer dependency. This allows anything greater or equal to 2.2.0 instead.
@codecov
Copy link

codecov bot commented Jun 26, 2017

Codecov Report

Merging #962 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #962   +/-   ##
=======================================
  Coverage   72.13%   72.13%           
=======================================
  Files           4        4           
  Lines         463      463           
  Branches      139      139           
=======================================
  Hits          334      334           
  Misses        129      129

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bbcdca7...ad4ab64. Read the comment docs.

@snyamathi
Copy link

Duplicate of #946

It's on their radar but not yet merged / released.

@shellscape
Copy link
Contributor

closing citing #946. new version was rolled out on the 7th

@shellscape shellscape closed this Jul 10, 2017
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.

3 participants