Great for static assets, potentially not-so-great for "load bearing" ;^) code

andai a day ago | parent | next [-]

Every time I try to get a npm based project running (or one of my forks of one), half the packages don't exist anymore or I need to spend hours fixing breaking changes.

It's usually more straightforward to just rebuild it from scratch — not to mention infinitely more satisfying — and that was true before AI!

	▲	gavinray a day ago \| parent [-]
		Language ecosystems tend to exist on a continuum. I love TypeScript but dread the dependency management because it's so often bit-rotted. On the other hand, I routinely build Java/JVM projects with dependencies that haven't been updated in a decade that compile without issues. Somewhere in the middle are most languages, I think.

▲

nonethewiser a day ago | parent | prev [-]

Yes it does depend on the dependency, and a static asset is on one end of the extreme.

It depends on the "load bearing" code. Obviously something like crypto is not something we should implement ourselves but core business logic would be "load bearing" in another way and is probably not something you want to farm out to a dependency.