feat(cli): add support for one-off version groups

[fregante]

Question

I'm using react 17, but in new packages in the monorepo I end up using npm install react, which adds react 19

syncpack's solution is to bump everything to v19 instead of having the new arrival match the existing versions.

How can I force syncpack to use v17 instead? Currently the process is very manual

Code of Conduct

• I agree to follow the Code of Conduct

[JamieMason]

This should hopefully work for you https://jamiemason.github.io/syncpack/config/version-groups/lowest-version/

[fregante]

It did, thank you!

[fregante]

Could this be exposed via CLI? I realized that when I do want to upgrade a package, then I have temporarily remove the config.

https://jamiemason.github.io/syncpack/config/version-groups/standard/#preferversion

Perhaps syncpack fix-mismatches --preferVersion lowestSemver

[JamieMason]

If you want the versions of some instances of react to stay on 17 while other packages update, you might be better pinning the react 17 ones? https://jamiemason.github.io/syncpack/config/version-groups/pinned/

[fregante]

No, I don't want to pin versions, I just want to differentiate between two actions:

• adding a dependency to a package without bumping it everywhere else (the dependency must match the existing one)
• updating a dependency by setting it once and running "fix-mismatches" (this is the default)

I suppose I could also use "syncpack update" but if I'm already in a package.json file, it's easier to alter an existing item version right there.

[JamieMason]

There's a good chance I'm misunderstanding you but this sounds like a typical case where you would use version groups, if you see the version groups section of the getting started guide it sounds very much like your situation.

Creating a version group for your old projects on its own would partition them from the new ones, and have them checked for mismatches internally, while the other group is kept from it. So all the react 17 stuff can be kept consistent with itself, while elsewhere the new stuff is kept consistent with itself.

Let me know if I'm not hearing you, but this is how it sounds from what I've read so far.

[fregante]

I think you misunderstood my second request.

This is not about each dependency or packages, it's about intent. Sometimes I want to use preferVersion lowestSemver, sometimes preferVersion highestSemver. It doesn't get deeper than picking between one of these on any specific day:

• syncpack fix-mismatches
• syncpack fix-mismatches --preferVersion lowestSemver

[JamieMason]

Ok, for all dependencies in your entire repo you will sometimes bump packages choosing the highest version, and other times the lowest?

EDIT: I can see a need for this for one off fixes without needing a config file.

syncpack fix --dependencies react --preferVersion lowestSemver

[fregante]

Yes like that