Skip to content
This repository has been archived by the owner. It is now read-only.

jspm upgrade command #706

guybedford opened this issue Apr 23, 2015 · 7 comments

jspm upgrade command #706

guybedford opened this issue Apr 23, 2015 · 7 comments


Copy link

@guybedford guybedford commented Apr 23, 2015

jspm update will always update dependencies within their ranges.

A jspm upgrade could be useful to update across major boundaries, perhaps with some kind of rollback facility.


Copy link

@crisptrutski crisptrutski commented Apr 23, 2015

Sounds pretty useful, but some issues spring to mind:

Does it release all the constraints at once? That could actually end in some dependencies getting knock backwards a bit. But releasing them just in time may mean that the command may need to do multiple passes or be run multiple times to converge. Then there's the chestnut of deciding the order to attempt updates in.

None of these are issues if you start with jspm upgrade X only though.

Copy link

@SandHilt SandHilt commented Jun 24, 2015

Or add list command like bower;

@guybedford guybedford added feature and removed discussion labels Aug 8, 2015
Copy link

@mikeobrien mikeobrien commented Oct 17, 2015

Yes, please! 👍

Copy link

@devmondo devmondo commented Oct 18, 2015


Copy link

@erenard erenard commented Nov 20, 2015

Hey guys, the install command does it.
Exemple :

jspm install aurelia-bootstrapper

=> upgraded to the last version

Copy link

@mikz mikz commented Feb 4, 2016

Coming from Rails world, the common workflow to bump major versions is to run bundle outdated and bump one by one, testing what works in the process. It is hard to imagine, doing automatic bump of all the dependencies, would not break everything. So I'd say #471 is more important, than this. Just to see what needs to be upgraded.

Copy link

@aTable aTable commented May 24, 2016

NPM has it's own version called "npm-check-updates"

Developers know not to brute force things so we probably should increment and test package upgrades one by one however...that's like watching paint dry. I'd like to spend less time upgrading packages and more writing code so jspm upgrade fits in wonderfully.

There will be times when it backfires for sure but deleting node_modules and reverting the jspm config.js file should be all I can foresee which is quite manageable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.