-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Interactive update packages command. #4895
Comments
It can be related #1223 |
it would be nice to have something like this package natively on bun: |
This seems to work well: https://www.npmjs.com/package/npm-check-updates#npm-check-updates |
for some reason this package doesn't work well in monorepos controlled by pnpm. I have different outputs when I run: bunx npm-check-updates -i -ws vs. pnpm up -i --latest -r |
NCU doesn't work well in monorepos indeed. This is one of the main point stopping me from trying bun in a monorepo. I'd love to see a recursive interactive upgrade command in bun :) |
FYI @3dos, this solution works very well for monorepo and bun: #1223 (comment) |
Can confirm that bunx npm-check-updates -i |
This should be an built in solution from bun. |
Yes |
You can use taze with any package manager. |
I want to work on this badly, but I need some help of what I will need possible to do this. |
Yes you can, but what they mean native to bun. |
This comment was marked as off-topic.
This comment was marked as off-topic.
In the meanwhile you can run Breakdown:
|
What is the problem this feature would solve?
Both
pnpm
andyarn
have a command where we can select which dependencies we want to update:This is extremely useful when we want to update only a few dependencies to be updated in a PR, for example.
References
What is the feature you are proposing to solve the problem?
Fine-grained way of selecting the dependencies that would be updated by bun.
What alternatives have you considered?
checking dependency by dependency in npm registry what's the latest version and do upgrade manually those versions.
Considerations
For workspaces, it would be cool if we could specify a flag
-r
that would read all package.json tracked and group them, like pnpm does.The text was updated successfully, but these errors were encountered: