Never use a dependency that you could replace with an afternoon of programming

Re:Never use a dependency that you could replace with an aft... by rootusrootus on Tuesday August 11, 2020 @04:51PM (#24125834)

There's lots of opinions on this, all with good justification. My current team leaves most dependencies unlocked and depends on good automated tests to sniff out broken dependencies. If necessary we lock dependencies to a particular version or range (e.g. <2.0.0). Once tested, we freeze for distribution.

Some people just never upgrade until they need to. That's workable, though when you do need to upgrade a package you may be spending the rest of the week working out a cascade of breaking changes.

[ Parent | on HN ]

Re:Never use a dependency that you could replace with an aft... by unilynx on Tuesday August 11, 2020 @05:11PM (#24126026)

If you only upgrade when you need to, but not necessarily to the latest versions, odds are that whatever breakage is caused by the latest nodejs/npm/etc incompatibility has already been documented in issue trackers or stackoverflow

[ Parent | on HN ]