You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
jvliwanag
changed the title
Support semver range as pin version while using exact version specifier
Support semver range on version group while using exact version specifier
Sep 9, 2024
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. OncecheckVersion
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.The text was updated successfully, but these errors were encountered: