-
Notifications
You must be signed in to change notification settings - Fork 157
Add yarn support. Fix #958 #963
base: master
Are you sure you want to change the base?
Conversation
|
Thank you @0xMRTT, can't wait to use it! |
|
Is this reasonable to run both npm and yarn? Do they have different sets of installed packages? |
|
For me it is enough if I can choose if I use npm or yarn. For me there are no use cases where I would run both at the same time. |
|
Okay, so we can add a new parameter to npm which is the path to the command for updating. By default it will be npm but you can change for yarn. What do you think ? |
|
The alternative is to do what topgrade already does for things like nala/apt: If tool X is a drop-in replacement designed to replace tool Y, and tool X is installed, run X instead of Y. In this case, yarn instead of npm. |
But if you have yarn and npm, maybe you need to choose |
|
Both would be for me good. Maybe it would be good to choose, to have a solution for the most users. |
|
I tested it on MacOS and it works for me |
|
What is to do, to get this done here? |
afaict roey is just gone for a bit. Gotta wait for them to come back. |
|
Merged at new fork because of inactivity by maintainer. |
|
Oh, what about creating an org for that ? |
Will be done in the future, currently in the progress of just looking at current issues and PRs |
|
I'll be glad to help you |
Here it is: https://github.com/topgrade-rs/topgrade |
Standards checklist:
cargo build)cargo fmt)cargo clippy)cargo test)If you developed a feature or a bug fix for someone else and you do not have the
means to test it, please tag this person here.
Fix issue #958 from @nicks-passiert