Closed nanianlisao closed 11 months ago
There are already many tools for that in npm.
Also, pnpm has built-in tool for that (I think that switching to pnpm
is the best for all projects).
But switching to PNPM cannot require cooperation from each project, especially when there are too many old projects
There are already many tools for that in npm.
@ai Can you help provide some similar tools? I am lacking in this area
I have 20+ open source projects and switched to pnpm in most of them.
If you don’t want to switch there are many tools already top update nested dependencies for npm.
Can you help provide some similar tools? I am lacking in this area
I saw them a few years ago when developed this tool.
Right now I don’t want to spend time for investigation again.
In pnpm it is just pnpm -r dependency
Anyway I don’t want to create a new tool and spend my time to support it, when there is a pnpm
All right, Thanks for your patient answer
Hey, we think the operation of updating the library version is a very general function. Have you considered separating it into a common basic library I'm looking forward to seeing this happen!