undefined | Better HN

0 pointsamelius5y ago0 comments

> Me too! I dread package upgrades because it can instantly turn into an all-hands-on-deck emergency, and these are just the stand-alone packages, not all the ones I mentioned above.

To all package manager developers: make sure you have a rollback function, and make sure it is flawless.

0 comments

4 comments · 2 top-level

fiddlerwoaroof5y ago· 2 in thread

Committing the package-lock.json file should do this for you: I always upgrade one dependency per commit and I put code changes in separate changes from upgrades. Also, you just have to learn which packages to avoid: react-router, for example, likes incompatible major version updates. Something simple like routedux that’s stable is almost always a better choice.

ameliusOP5y ago

With all the different package managers out there, it's just not much fun to keep track of all the rules and special cases for each tool. Better to just have a "--rollback" option.

fiddlerwoaroof5y ago

Isn’t this solved more generically by version control? As long as your package manager uses files to control the packages searched for, them you commit those files between upgrades and revert them to rollback. nix handles this at the system-level by making your system configuration match a declarative specification.

harrygeez5y ago

or... you can rollback to an older version yourself

j / k navigate · click thread line to collapse