Comments (4)
I've decided not to do this as there are a lot of good tools out there for updating npm dependencies, I don't want to dilute the focus/purpose of syncpack too much. Thanks anyway for raising this.
from syncpack.
Thanks @mesqueeb, this is a good idea and I may add this as a feature in the future. It would be low priority because there are other tools which do this, but it would fit well and could be a nice addition.
Incase it's useful to you, the way I do this today is to use npm-check-updates to update the versions in package.json files, then run a regular install afterwards.
- Run
ncu -u
to update the root package.json. - Run
lerna exec 'ncu -u'
to update each package.json in the monorepo.
If lerna is installed locally to your project instead of as a global dependency you can run this instead...
If you use yarn:
yarn lerna exec 'ncu -u'
Or this if you use npm:
node_modules/.bin/lerna exec 'ncu -u'
EDIT: The above steps will update the package.json files only, you can then do an npm install
afterwards.
from syncpack.
Reopening as work has actually started on this, things are a bit different now and I think this could be a good fit.
Please subscribe to this issue to track progress.
Thanks @mesqueeb.
/cc @cimchd @hgenru (👍🏻'd this issue)
from syncpack.
Released in 10.7.2
from syncpack.
Related Issues (20)
- fix(core): ignore missing snapTo dependencies HOT 7
- feat(core): add specifier type for * & latest HOT 5
- feat(update): list all newer versions, not only newest
- Question on using $LOCAL in a semver group HOT 3
- feat(update): add repository url to the prompt HOT 2
- feat(cli): throw when an entered command is invalid HOT 4
- [dependency maintenance] @effect/match -> effect migration HOT 1
- fix(workspace): add support for workspace:^ HOT 4
- fix(local): allow missing .version if not depended on HOT 4
- fix(cli): include names of ignored packages HOT 1
- question(rcfile): how to require a shared configs package? HOT 2
- question(core): can syncpack manage tsconfig.json files? HOT 3
- question(core): should syncpack bump package versions after fixing mismatches? HOT 3
- question(config): how to pin local packages to "workspace:*"? HOT 20
- fix(update): mismatches occur after updating with syncpack 12.3.0 HOT 1
- feat(lint): output more detail about invalid formatting HOT 4
- question(config): how to pin local packages to "workspace:*"? (2) HOT 4
- question:(groups): How to ignore minor version mismatches? HOT 1
- Feature Request: Disallow redefining dependencies already defined in the root
- feat(fix): preserve original formatting HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from syncpack.