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.
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.
jspm upgrade X
Or add list command like bower;
Yes, please! 👍
Hey guys, the install command does it.
=> upgraded to the last version
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.
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.