Special keywords for npm

Drivers/components are an important part of the Cycle.js ecosystem. Yet finding community libs isn’t particularly easy at the moment.

One thing that lots of tools use is to promote usage of a particular npm keyword for their packages. This can help developers find those tools, or power search pages on the project’s site itself.

I think a similar system could work well for Cycle.js drivers and components.

Prior art:

• Grunt plugins
• Gulp plugins
• Yeoman generators
• Ember Addons

If y’all think this is a good idea, I think the next steps could be:

1. decide on a keyword (cyclejs-driver/cyclejs-component, for instance)
2. promote it on the website in the proper section
3. either link to an npm search, or build your own search on the site

Cycle.js seems cool – I’d like to see the community around it grow, and this could help with that.

---

Also, without a special keyword, it can be tedious for community members to build discoverability around their modules. It requires adding a whole bunch of permutations, which seems silly and isn’t as useful as having one “official” keyword.

[staltz]

Because cycle is not good for search engines, let’s use cyclejs (like the GitHub org) and Cycle.js in other texts, like in conference talks, etc. Drivers and libraries could be named just cycle-foo, as they already have been.

[staltz]

Unfortunately Cycle packages at @cycle/foo can’t even be searched on npmjs.com because NPM still hasn’t built search feature for scoped packages.