Re:Old Code Gets Younger Every Year
by speedgoose on Monday June 08, 2020 @05:29PM
(#23461026)
Because it's one line to a dependency with a name, a documentation, a bug tracker, many users, and that could be improved in the future.
If you are scared about packages behaving differently, you should know that npm has lock files that describes your full dependency tree with versions and checksums.
Re:Old Code Gets Younger Every Year
by majormajor on Monday June 08, 2020 @05:53PM
(#23461220)
"Could be improved in the future" is a risk when it comes to a simple utility function that does a simple thing that you don't want to change.
In the same way that someone constantly tweaking your utility functions in your own project would be a risk - and you'd understandably want to code review all that - the more you choose to (or have to) outsource "trivial" stuff, the more brittle your project is.
"Why depend on that as a dependency rather than just have a copy directly in my project that I know will never behave any differently?"