We're building a system for incrementally upgrading our monorep (for which we'll also need https://github.com/Thinkmill/manypkg/issues/13).
After a user runs yarn add, we run manypkg fix to make sure the right version was added. But if a dependency is under incremental upgrade that can have unexpected consequences.
If a developer runs yarn add react in pkgD, manypkg fix will updated all the other React dependencies down to 1.0.0, undoing the incremental upgrade. By adding a --only (open to better names), we want to have manypkg fix only update the current directory, in this case pkgD, so that only pkgD's package.json is fixed.
We're building a system for incrementally upgrading our monorep (for which we'll also need https://github.com/Thinkmill/manypkg/issues/13). After a user runs yarn add, we run manypkg fix to make sure the right version was added. But if a dependency is under incremental upgrade that can have unexpected consequences.
If a developer runs
yarn add reactin pkgD, manypkg fix will updated all the other React dependencies down to 1.0.0, undoing the incremental upgrade. By adding a--only(open to better names), we want to have manypkg fix only update the current directory, in this case pkgD, so that only pkgD's package.json is fixed.We're more than happy to contribute this back