3 ms·
> Those language-specific package managers do not auto-update the packages you have installed with them Adding a new package often triggers a re-resolve of all
by gugagore 6y ago
> Those language-specific package managers do not auto-update the packages you have installed with them
Adding a new package often triggers a re-resolve of all installed versions. Whether any updates happen at that time depend on how you've set versions bounds: e.g. https://stackoverflow.com/questions/48911625/npm-how-to-install-a-new-package-without-update-or-add-packages-described-on-p https://stackoverflow.com/questions/48911625/npm-how-to-inst...
> the conclusion that auto-updates are a "better experience"
I don't know that they are necessarily a better experience overall, but it is certainly a worse experience to run into a bug or limitation that has already been resolved in a newer version.
- pseigo 6y agoIt's likely that you'll run into some bug for any software release. What you can control is whether the user makes a deliberate choice to upgrade; the risk of bringing in new bugs or breaking changes may outweigh the cost of dealing with the bug, so in this situation, upgrading for a fix has known benefits and is intentional. This thought process is helpful for pitching your case with stakeholders as well.