In my view it is objectively wrong to create trivial npm packages yes. If we look at the npm ecosystem as a commons, that person is polluting it. Of course you

In my view it is objectively wrong to create trivial npm packages yes. If we look at the npm ecosystem as a commons, that person is polluting it. Of course you could say it's namespaced to one account, so what's the harm? In my view, plenty: - package searches will show these packages due to the inflated usage from transient deps. - installs are slower due to the package noise. - increased attack surface when they are used - cultural normalization of throwaway packages Probably more.