To help explore Elm packages and find the relevant ones easily, I made Elm Package Catalog which lists them by category. So far I’ve added ~260 packages.
Another thing I was interested in is making it easier to find gaps in the package ecosystem. If somebody is looking for a project, they can easily find something that’s not already been done (at least once the catalog is more complete).
An obvious thing would be to add some metrics, but I’m wary of reproducing the NPM rat race if I show GitHub stars and the like. Would love to hear ideas on what would be useful to show about packages.
Interesting idea but not sure how I could get the data, short of people reporting in. That, however, would be error-prone as dependencies change. I suppose I could get dependencies for stuff that’s on GitHub, and that would yield some examples.
I can see how this would be useful from a package author’s point of view, but my main goal is to augment the search that’s already available on package.elm-lang.org.