npm-modules is amazing. It's indexing is pretty good and I love the fact it shows me modules by unknown authors because people I know on github have used that module.
On Fri, Sep 20, 2013 at 11:35 AM, Mathias Buus Madsen <mathiasb...@gmail.com > wrote: > On and off over the last six months we've built a search engine for > finding modules, http://node-modules.com. It uses several parameters and > some cleverness to give you great results quickly. > > While using it ourselves we have noticed a paradigm shift in the way we > work, which has been really interesting. The last part of this post will go > over that. > > > Node-modules.com and what it does > There are already two search engines in the node community (apart from > npmjs.org), http://eirikb.github.com/nipster and http://nodetoolbox.com. > However, node-modules.com have something new contribute with. We set out > to give you the absolute most relevant results at the very top. > Node-modules.com uses different parameters to rank all modules and give > better results: > > * Name, keywords, and description of the module (cleverly done so that > 'parse' and 'parsing' are alike) > * Number of other modules dependant on this module > * Number of stars on github > * If you follow the author > * If the module is used by an author you follow > * If you have starred another module by the same author > > Some of these parameters require you to log in with github, but even > without it you get great results. By starring more modules and following > your favorite authors on github you'll improve your search results. > > That's about all there is to it. Why not try some of these: > The top router modules, http://node-modules.com/search?q=router > The top mongo modules, http://node-modules.com/search?q=mongo > Or all the modules substack has created, > http://node-modules.com/search?q=@substack > > > Command-line version > Of course there's also a cli tool for node-modules.com > > $ npm install -g node-modules > $ node-modules search web framework > > > A paradigm shift? > But what was this with a paradigm shift? To avoid this post being too > lengthy, and miss the point, we wrote it about on our blog, > http://www.reddit.com/r/node_modules/comments/1msh9n/a_paradigm_shift/ > > > Thoughts? > Feedback is much appreciated, @node_modules or the blog, > http://reddit.com/r/node_modules > > Pull requests accepted, http://github.com/mafintosh/node-modules > > // Mathias Buus, http://github.com/mafintosh > // Tobias Baunbæk, http://github.com/freeall > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nodejs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
