Well let's do more of that :)
Yeah this could lead to a better maintained kind-of stdlib for js.
But it might also lead to an even more fragmented ecosystem, where it is most lucrative to publish a lot of one-liners and hope that a big project will use it somewhere in it's dependency graph.
It would also leave other kinds of packages more or less unpaid. Take for example a cli app. No one will depend on it, while it could have millions of downloads at the same time. On the other hand, that's a different kind of problem as it wouldn't have such an impact on the generell ecosystem and could be targeted by donations, one time payments or something like that.
The revenue split is certainly a tricky question, however at this point it seems obvious that:
When it's easier to buy it people tend to do so. I definitely think it's worth working around that idea.
The problem I see is we're not dealing with people, we're dealing with organizations. Its a bit odd but I don't think a company would decide to pay for such a service.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.