Description
- I'd be willing to implement this feature (contributing guide)
- This feature is important to have in this repository; a contrib plugin wouldn't do
Describe the user story
I have a project which uses next and next-offline as dependencies. The package.json of these two packages are as below:
// next/package.json
{ "dependencies": { "webpack": "4.44.1" } }
// next-offline/package.json
{ "peerDependencies": { "webpack": "^4.19.1" } }
next-offline has webpack in its peerDependencies, so I have to also add webpack into my project's package.json to avoid the warning from Yarn. Since I don't actually use webpack directly and I don't care which version of webpack I'm using, I simply write "webpack": "^4" in package.json
// my-project/package.json
{
"dependencies": {
"next": "^10.0.4",
"next-offline": "^5.0.3",
"webpack": "^4"
}
}
The latest webpack@^4 version today is 4.44.2, which cause Yarn to install two version of webpack in my-project:
# my-project/yarn.lock
"webpack@npm:4.44.1":
version: 4.44.1
"webpack@npm:^4":
version: 4.44.2
Install two versions of the same package (not specifically webpack) could cause some issues.
Describe the solution you'd like
Implement yarn dedupe --strategy fewer. This command should update the yarn.lock above to:
# my-project/yarn.lock
"webpack@npm:^4, webpack@npm:4.44.1":
version: 4.44.1
I'm using renovate to manage my dependencies, which can run npm dedupe or yarn dedupe after every update (docs). This means that I don't have to run yarn dedupe myself so this is an acceptable solution for me.
Describe the drawbacks of your solution
Please let me quota the document from yarn-deduplicate --strategy fewer:
Note that this may cause some packages to be downgraded. Be sure to check the changelogs between all versions and understand the consequences of that downgrade. If unsure, don't use this strategy.
Describe alternatives you've considered
There is a RFC to fix this kind of issue at #1001 (which has an almost identical example). However, it seems that this PRC hasn't been implemented.
why not make it a plugin
Because we already have yarn dedupe --strategy highest.