3 ms·
> On the other hand, each dependency you add creates a little bit of risk: that the package will be updated in a way that breaks your application, or the packag
by pc86 11y ago
> On the other hand, each dependency you add creates a little bit of risk: that the package will be updated in a way that breaks your application, or the package maintainer will go rogue, or the package will get hijacked.
If your development environment is such that you can't test these things before going into production, and that production updates its packages on its own, then you have much bigger (and harder to fix) issues that dependency hygiene.
- nyan4 11y ago> before going into production How about 3 years after a release? 5, 8, 10?
- philipov 11y agoIf you haven't upgraded your packages in 10 years, you've got nothing to worry about ;)
- zenlikethat 11y agoThe risk is much bigger than simple lifecycle testing will account for. Upstream micro libraries could easily disappear or have bugs, leaving you spending more time trying to workaround than if you had just written the darn thing yourself in the first place. Or, you suddenly have a new requirement that doesn't play well with the lib. Programmers loves dependencies because it lets them pass the buck, but each and every 3rd party module is a potential time bomb waiting to happen.
- michaelmcmillan 11y agoHow can a test detect a hijacked dependency that acts exactly like the original, but with a backdoor?