- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
It’s great when you find the perfect package but then see the last update was four years ago.
Or…
I mean, it was built to help put JavaScript where it doesn’t belong, so expectations of elegance and cleanness should be limited.
Isn’t the usual approach to just include every single one of them anyway?
No. You just include one or two. Those will include all the others, not you.
Same with Ruby at this point. Someone needs to create a new RubyGems without all the c. 2009 abandonware shit.
…and Python, Java, and GoLang.
At least with Java, many of the cornerstone packages have a corporate sponsor maintaining them.
I don’t know about the other languages but most widely used JavaScript packages also have corporate backing
Perl. CPAN has been around for a long time and has some packages in it that are older than other languages’ entire repositories, I swear.
The sad part is that so few npm packages are really necessary…
If the package isn’t tree shakeable, I try not to use it.
