-
-
Notifications
You must be signed in to change notification settings - Fork 187
Closed
Description
In commit 79987fc, which is included in 3.2.0, the peerDependency argument of webpack got changed from >=4.44.2 to ^4.44.2. This means that from 3.2.0 on, Webpack 5 is not allowed as a peer dependency.
- Manifest Plugin Version: 3.2.0
- Webpack Version: 5.46.0
- Operating System (or Browser): Win 10
- Node Version: 14
- Link to reproduction (
⚠️ read below):
Repro
With NPM 7:
- cd to some empty directory
npm install webpack@5npm install webpack-manifest-plugin
Expected Behavior
Successful installation
Actual Behavior
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: webpack@5.46.0
npm ERR! node_modules/webpack
npm ERR! webpack@"^5.46.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.44.2" from webpack-manifest-plugin@3.2.0
npm ERR! node_modules/webpack-manifest-plugin
npm ERR! webpack-manifest-plugin@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Additional information
Running npm install webpack-manifest-plugin@3.1.1 works fine.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels