[BUG] Seemingly erroneous peer dependency conflict (ERESOLVE)

[markmckenna]

Using [email protected]

package.json:

{
  "name": "project-a",
  "dependencies": {
    "webpack": "^4.41",
    "webpack-dev-server": "^3.9"
  }
}

Actual

$ npm install --strict-peer-deps=true
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0 || ^5.0.0" from [email protected]
npm ERR!   node_modules/webpack-dev-server
npm ERR!     webpack-dev-server@"^3.9" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from [email protected]
npm ERR! node_modules/webpack-dev-middleware
npm ERR!   webpack-dev-middleware@"^3.7.2" from [email protected]
npm ERR!   node_modules/webpack-dev-server
npm ERR!     webpack-dev-server@"^3.9" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --no-strict-peer-deps, --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

NOTE: Without --strict-peer-deps this resolves fine, without any (related) warning.

Expected

It seems like these peer dependencies should resolve just fine:

• I full-depend on webpack major 4 and webpack-dev-server
• webpack-dev-server peer-depends on webpack major 4 or 5 and webpack-dev-middleware
• webpack-dev-middleware peer-depends on webpack major 4

It seems like it's maxing out webpack-dev-server's acceptable range first, then resolving that against other packages in the repo, even though there's a non-peer dependency that should be pinning it to v4, which is also acceptable to webpack-dev-server.

[isaacs]

Fixed in latest release.

[markmckenna]

Apologies! I tried to update to latest yesterday and stayed at 7.0.3. I'll bring myself up.

[saabdal]

Hey All, what do you that this is fixed in the latest release....?