3 ms·
You're using a different, not hosted anymore package, three times a week? That's somewhere between very unusual and downright absurd. Yes you can find edge cas
by lucianbr 2y ago
You're using a different, not hosted anymore package, three times a week? That's somewhere between very unusual and downright absurd.
Yes you can find edge cases with problems. Using this as an argument for "breaks 3 times per week" does not hold.
- TeMPOraL 2y agoNo, I was using this as an argument for why I don't expect Node projects older than a year or two to be buildable without significant hassle. (Also note that outside the web/mobile space, projects that weren't updated in a year are still young, not old. "Old" is more like 5+ years.) The two things are related. If your typical project has a dependency DAG of 1000+ projects, a bug or CVE fix somewhere will typically cause a cascade of potentially breaking updates to play out over multiple days, before everything stabilizes. This creates pressure for everyone to always stay on the bleeding edge; with a version churn like this, there's only so many old (in the calendar sense) package dists that people are willing to cache. This used to be a common experience some years back. Like many others, I gave up on the ecosystem because of the extreme fragility of it. If it's not like that anymore, I'd love to be corrected.
- afiori 2y agoI don't know if it is still as fragile as you remember but if you just never update your package-lock then it is super stable as you (transitive) dependencies never change. The non-trivial exception being if some dependecy was downloading resources on the fly (maybe like a browser compat list) or calling system libraries (eg running shell commands)