it’s based on having “react-component” in the keywords so false positives are non-existent, and since there are several search sites that use the same keyword, any react component worth knowing about uses it, so false negatives are also low.
The whole npm registry seems to lack the notion of categories, so I guess trying to get something going specifically for meteor may not be very intuitive.
one approach could be that meteor by convention recommends usage of certain keywords, in addition to meteor, and then for the crawler, it can categorise by using meteor and the additional key words / tags.
Yeah I think it would be super awesome if the next version of Atmosphere also indexed NPM packages with a certain keyword. Regarding categories, does anyone know of a package system existing today that does this? It would be nice to follow a successful example.
I think meteor-platform could be a fine keyword.
@avital@benjamn I think this is a pretty simple but high leverage thing we could do, can we write this somewhere in 1.3 release plans?
The majority of the packages listed are prefixed react-*, but not all. Packages not prefixed with react do have keywords react, react-component, react element, etc. So you could use a combination of the two approaches.