Support semver range on version group while using exact version specifier

[jvliwanag]

Description

Using exact version on dependencies in package.json makes it simpler to figure out what version is being used without needing to dig onto lockfiles. This is configured on syncpack as a semverGroup with range: ""

When setting up version groups however, while it is possible to lock onto a version by setting a pinVersion; it is not currently possible to specify some semver range specifier to some allowed version range.

For example:

I want storybook deps to be any of ^7.0.0 version. But when updating or linting, it should save it as an exact version -- 7.6.20 for instance.

Suggested Solution

Perhaps introduce a new field called checkVersion on version groups to check against. Once checkVersion is there though, for groups of dependencies, it is not enough that they pass through that semver check. It should further be assumed that all dependencies under that version group should all point to the same version.

[guillempuche]

Interested

[JamieMason]

Thanks both, this sounds a good idea.

I've been thinking of some kind of merging or aliases feature which would support this, where families of dependencies are treated as one. Like you said, this could avoid needing to use pinVersion in scenarios like Ensure AWS SDK dependencies always have the same version.