Filter packages using metadata

[waynevanson]

I would love to be able to find the right package/s for the right job, in a case where searching for the term might not find it for me.

Currently the only way to figure out what each package does is with either the search bar, experience or time sensitive lists curated by other users (usually in blog posts).

In a best case scenario, the user can select from a list of categories to include and exclude them from visible packages. A package can have zero or more labels.

Having metadata for packages means users could search for packages that work in the browser, or packages compatible with node, or what ecosystem they're compatible with.

What are the community thoughts on something like this?

I'm brand new to purescript, so coming from node/typescript means that 90% of my knowledge of the package usefulness is obsolete. In any case, something similar to the proposed would help new users experience the joys of functional programming and purescript.

[hdgarrood]

This sounds sensible to me (see also #147). We're currently working towards getting a new package registry set up over at https://github.com/purescript/registry, as the Bower registry is no longer accepting submissions. This data would need to be stored in the registry, so there is probably a better place to discuss this than here. Having said that though, right now it's still in an early state, and this might be something we might want to consider slightly further on in its development.