search

Thinkmill / manypkg

☔️ An umbrella for your monorepo
MIT License
892 stars 48 forks source link

Feature Request: Option Flag to always use Highest Semver Range #129

Open fbartho opened 2 years ago

fbartho commented 2 years ago

Currently, manypkg check and manypkg fix decide to resolve dependency versions based on the most commonly witnessed range in the repo. -- Only when there are equal quantities of each range specifier do we select the highest range:

https://github.com/Thinkmill/manypkg/blob/b8b914441995ad267a490251d443665fb999e32b/packages/cli/src/checks/utils.ts#L152-L158

Would we support a flag --use-highest-range on each command to force this algorithm to select the highest range for a given dependency?

Alternative: add a .manypkg.config.json this and other flags?

I'm happy to contribute this code change if a maintainer can indicate if they'd accept an appropriate PR implementing this.

jrolfs commented 2 years ago

I also prefer this behavior and would be happy to help.

I do worry, though, that y'all are trying to avoid introducing unnecessary configuration... if so is there another recommended way to upgrade a dependency accross an entire monorepo to a specified range?