Which are non-breaking updates
dgk last edited by dgk
I like to keep my packages up to date but I tried the major updates as shown and it breaks quasar dev. (as of Oct 3, 2017)
What can I safely upgrade at this time?? Sometimes is it better to start a new quasar app with the latest cli and move my code rather than upgrade all the packages?
ssuess last edited by
I have the same question
Read about semver notation here: http://semver.org/
Hopefully all these packages follow this notation. I know most of them do.
As it’s highlighted by your tool, major updates come with breaking changes. It’s safe to go with the minor updates though.
Before jumping in and upgrading to a newer version, it’s best to ask yourself what are the benefits of upgrading. From my own experience, most of the times you will spend time debugging why some package stopped working for a certain scenario. Latest does not always mean better.
dgk last edited by
I get semiver use and that major version changes can be breaking
As to “latest doesn’t mean better” at the speed that things are changing if one doesn’t address major dependency changes eventually in a year or so you may find yourself in deprecation land and eventually your work becomes obsolete and/or you find yourself trying to “fix” a lot of major dependency upgrades at once. Witness a year ago quasar was not even nearly as usable as is today and I happily moved to .14 with its breaking changes.
Beyond that maybe a major update has improved security and/or features. Most browser and nodejs now support most of ES6 which has all happened in the last year. Many significant repos are refactoring for async/await. Lots of reasons to keep current if just not to become personally obsolete.
So my question again is…what if any of the major updates I listed (using npm-check repo) have you, the developer, attempted so I don’t waste time seeing which ones break and which ones don’t. If the answer is none…well ok.