Describe the bug
Installing webpack-cli@4.0.0-beta.1 still adds the latest webpack @4.x.x to the node_modules folder, even though it directly depends on webpack@^5.0.0-beta.3.
The dependency comes to play via webpack-cli -> @webpack-cli/init -> @webpack-cli/generators webpack@4.x.x
To Reproduce
Steps to reproduce the behavior:
- Go to a new folder
- npm init
- accept defaults
- npm install webpack@5.0.0-beta.11 --save-dev
- npm install webpack-cli@4.0.0-beta.1 --save-dev
Expected behavior
I would expect it to only need the already-installed 5.0.0-beta.11.
Additional context
I'm trying to avoid an issue with fsevents@1.2.11, which is an optional transitive dependency of webpack@4 (webpack -> watchpack -> chokidar -> fsevents). I'm willing to move to the beta of webpack 5 for this particular project, but I'm running into this issue with webpack-cli. With that version of fsevents being dropped into node_modules, I can't ever run npm ci, even though we don't actually use anything that would be impacted.
Describe the bug
Installing webpack-cli@4.0.0-beta.1 still adds the latest webpack @4.x.x to the node_modules folder, even though it directly depends on webpack@^5.0.0-beta.3.
The dependency comes to play via
webpack-cli -> @webpack-cli/init -> @webpack-cli/generators webpack@4.x.xTo Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect it to only need the already-installed 5.0.0-beta.11.
Additional context
I'm trying to avoid an issue with fsevents@1.2.11, which is an optional transitive dependency of webpack@4 (
webpack -> watchpack -> chokidar -> fsevents). I'm willing to move to the beta of webpack 5 for this particular project, but I'm running into this issue with webpack-cli. With that version of fsevents being dropped into node_modules, I can't ever runnpm ci, even though we don't actually use anything that would be impacted.