Before moving an existing application into a monorepo there's no automated way to check if the dependencies in the application will align with the existing dependency versions in the monorepo or if they'll cause the one-version check to fail.
Proposed Solution
Add a -f --file option to the one-version check command where we can pass an arbitrary (local) file path to check for one-version compatibility.
Problem Statement
Before moving an existing application into a monorepo there's no automated way to check if the dependencies in the application will align with the existing dependency versions in the monorepo or if they'll cause the one-version check to fail.
Proposed Solution
Add a
-f --fileoption to theone-version checkcommand where we can pass an arbitrary (local) file path to check for one-version compatibility.For example:
This would allow us to preview the output as if we had already moved the new
package.jsoninto the monorepo.Alternatives Considered
Manually move a
package.jsoninto the monorepo and runyarn one-version checkto see which versions do not match.Additional Context
No response