3 ms·
I get the ridiculousness of those tiny packages. On the other hand I also hate to have my codebase bloated by some kitchen-sink "util" package of which I'll use
by xg15 5y ago
I get the ridiculousness of those tiny packages. On the other hand I also hate to have my codebase bloated by some kitchen-sink "util" package of which I'll use about 0.1% functionality. (while, if I were really strict, I'd also have to audit and track the remaining 99.9% of the code.)
Tree-shaking can help at least keeping the build artefact small, but it doesn't help with the codebase during development.
Of course there is still a difference between fine-grained dependencies and things that shouldn't be dependencies in the first place.
- ratww 5y agoThere is a sane middle ground between tiny and bloated, though. I don't see how using a false dichotomy justifies the issues we're complaining about. Especially when most of those packages are almost never used by themselves, and are instead part of a meta-package with dozens of dependencies.