Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
jspm upgrade command #706
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
This was referenced
Oct 24, 2015
Coming from Rails world, the common workflow to bump major versions is to run
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
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.