3 ms·
On this note, I wish more npm library authors would emulate sindresorhus's approach of making small packages that each do very specific things in a predictable
by crooked-v 3y ago
On this note, I wish more npm library authors would emulate sindresorhus's approach of making small packages that each do very specific things in a predictable and well-documented manner.
- whstl 3y agoHell no. This person is probably the worst offender in terms of supply-chain problems and bloat in the NPM ecosystem. A terminal spinner ("ora") with 15 dependencies (including transitive) is not an example of good design. Inflating the numbers of downloads in your own packages is doing no good to the world of software.
- brnt 3y agoWhat you hope for is shallow dependency trees, not too branchy, but probably also not branchless (an indicator of vendoring). Larger projects will have and likely require depper trees through, but the branchiness should be relatively independent. I wonder if this has ever been formalized.
- whstl 3y agoWhat I hope for is for code that is actually auditable, and doesn't pull a lot of unused bloat just to pump up someone else's vanity metrics. This applies for large and small projects. Babel also doesn't need to do what it does: it pulls a couple hundreds of non-reusable sub-packages even though it's all written by the same people and maintained in the same monorepo.
- Aeolun 3y agoHonestly, I’ve often considered chunking all those libs into a single big one to eliminate 50% of my npm dependency chain.