The culture of micro-packages is mostly pushed by people with financial interests. The modus operandi is to add a semi-useful package to a popular project, and

The culture of micro-packages is mostly pushed by people with financial interests. The modus operandi is to add a semi-useful package to a popular project, and then divide said project into other sub-projects just to bump the numbers. Then those individuals start claiming that they have "25 packages that are foundational to the web infrastructure", while in fact it's just a spinner that has 24 dependencies, some of those being one-liner packages. Parallel to that we also have things like Babel, which has hundreds of packages, a huge chunk of them being almost empty and only triggering flags in the core package.