Options to run upgrade one by one and run a command after to check if everything is ok

[jordan-boyer]

Clear and concise description of the problem

First of all thx you for the amazing tools =)

I would like to have an option to upgrade dependencies one by one and run a command after it (like npx taze --oneByOne --command npm run test).

We could also provide a command for committing just after upgrade with a custom message (like npx taze --oneByOne --commit 'chore: upgrade %n %cv to %v' where %n is the package name %cv is the current version and %v is the updated version)

I think the option --command can be globaly available (chainable with other options) since you might want to run a command juste after and upgrade and roll back if this command fail.

Option --commit should only be available with the --oneByOne option.

(feel free to change options name and send me feedback on it)

Suggested solution

If you like the idea I can try to implement it =)

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[antfu]

You can already ad -I for interactive select, isn't that enough for your case?

[cbbfcd]

A great tool, thanks to the author.
It looks like a similar scenario to the one I'm facing, let's say I have a monorepo project with more than 20 sub-projects, and if I change them one by one via -I, my zsh just won't work properly~!
It would be nice to have a command or configuration to specify that only certain dependencies under a packages/foo should be updated, so that incremental upgrades can be done to ensure business stability.

[jordan-boyer]

I'm so sorry for the delay.

-I seems to be a good start but it does not really work for my use case.
Like I said before, I want to upgrade one dependency and then directly run a command after it and if the command pass (e.g: exit code 0) then i want to proceed to the next upgrade.

I don't want to do this manually because on large legacy project it can be tedious to do so.