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
Currently syncpack update updates all packages to their latest version, regardless of semver range specified. I'd like to be able to use update to bump packages to their latest version, within the semver range they are defined with, i.e. "syncpack": "^12.0.0" would resolve to "^12.4.0", rather than "13.0.0".
This would allow me to use syncpack as a dependabot replacement in the CI for large monorepos whilst making use of the linting/formatting syncpack provides.
Suggested Solution
As above. Provide a flag to the update command to indicate we want to bind the updates to their current semver range.
If a dependency is defined with different ranges across the repo, throw an error.
Happy to help out on this one if you think it's a good idea. Thanks for all the hard work you put in on syncpack. ❤️
The text was updated successfully, but these errors were encountered:
oev-chrisbennett
changed the title
update command can be fixed to a semver range
feat(update): update command can be fixed to a semver range
Sep 17, 2024
Thanks both, the update command needs a bit of work:
As I mentioned, the update command is new and currently quite buggy. Every other command has lots of tests and good confidence they are working, but update and prompt do not.
In the meantime I would wait before using this command. A rewrite of syncpack is coming in the next month or so and the situation should improve then.
– #210 (comment)
The challenge has been just getting the time, I'd love to get the rust port done and then come back and work on update.
But in short yes this feature is a good idea and should be included 👍
Description
Currently
syncpack update
updates all packages to their latest version, regardless of semver range specified. I'd like to be able to useupdate
to bump packages to their latest version, within the semver range they are defined with, i.e."syncpack": "^12.0.0"
would resolve to"^12.4.0"
, rather than"13.0.0"
.This would allow me to use
syncpack
as adependabot
replacement in the CI for large monorepos whilst making use of the linting/formattingsyncpack
provides.Suggested Solution
As above. Provide a flag to the
update
command to indicate we want to bind the updates to their current semver range.If a dependency is defined with different ranges across the repo, throw an error.
For a real-world example see the
bun update
command inbun
's CLI.Help Needed
Happy to help out on this one if you think it's a good idea. Thanks for all the hard work you put in on
syncpack
. ❤️The text was updated successfully, but these errors were encountered: