-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(update): define constraints which only apply when updating #244
Comments
Interested |
Closing as a duplicate of #204 until/unless I hear otherwise. |
#204 is pre-released in 14.0.0-alpha.3 |
Hi @JamieMason thanks for getting onto this. While dependency groups are quite useful, I'm not sure I follow how this would solve this issue. In particular, how would I use semverGroup with |
Thanks @jvliwanag I think I understand what you mean now, I was getting a few other issues confused with this. The |
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: