Yes, but fetching full npm package metadata (which includes the readme) for 100s of packages was really slow. I'll see if there's some other approach (perhaps getting the readmes from GitHub, or perhaps pre-processing all package readmes) that might work.

I did not know other terminals struggled to display emoji. I'll test out a default Windows Bash and Ubuntu terminal to get some concrete data points and use a fallback if necessary.

Interesting idea. What do you envision such a partnership would look like?

Here's how I think about this. OpenCollective solves the problem of accepting payments and allocating those payments to maintainers in a transparent way (Patreon does this too, to some extent).

`thanks`, on the other hand, just lets you know that a maintainer is asking for donations and directs you to their donation page which may be on OpenCollective. For example, these ones are: https://github.com/feross/thanks/blob/c203cc0248fe339e9ea4b8...

I suppose `thanks` could do more, e.g. accept payments directly from the command line, or ask how much you're willing to donate and then suggest an allocation to each maintainer/team. But I wanted the v1 of this product to be super simple. It merely raises awareness that you may have dependencies looking for donations, but doesn't prescribe how much to donate, which platform to donate on, or whether to donate at all.