Closed ralphtheninja closed 6 years ago
Or use the level/community
repo. Which might suit better because of the name.
Not sure I understand the goal?
The goal would be to be able to query for level related modules. Today this is basically lore, since you need to do research yourself, ask someone or check the awesome page. Maybe just overkill :)
Though I agree npm has a huge gap when it comes to this, I don't like adding a dependency just for discoverability.
How about gulp's approach? They actively recommend authors to use the gulpplugin
keyword, and have a website that queries for this. Or well, the npm and npms websites do that too, as well as the cli: npm search keywords:level
. We'd need a standard keyword.
doesn't every module (dev)depend on level* already?
This way we can have repos dev-depend on it which will help with quering from npm to find level related modules.