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 int
> open pull requests commit activity
There are some modules so simple that the code will never change. I have
several of my own that are untouched over a year but I rely on them
heavily. I do look at commit activity myself. I'm just saying it isn't
always accurate.
The opposite example is soc
Indeed, it shouldn't focus indication but a combination of all, open pull
requests, lots of issues and nearly no commits is a good indication that the
project is dead and should not be promoted actively. And as much as it hurts me
to say this, socket.io is indeed a good example of this.
On Frid
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 wrote:
> On and off over the last six months we've built a search engine
@Raynos:
Glad you like it! (assuming you mean node-modules)
We actually find ourselves starring a lot more stuff on Github now since
it'll mean our search results will become better (that's actually how I
found your xtend module).
@3rdEden
Currently it adds a penalty to the module rank if the mo
In addition to stars on github it should really take the amount of issues, open
pull requests commit activity in consideration when recommedating modules. So
it can filter out all the dead and unmaintained projects which are likely to
die soon.
On Friday, September 20, 2013 at 8:35 PM, Mathias
I would also be concerned about false positives when trying to determine if a
project is abandoned. If you do try and implement this, please create a way for
people to see how the scoring works, so that they can help you refine the
algorithm.
:Marco
--
--
Job Board: http://jobs.nodejs.org/
P
The entire search engine is open-source. You can find it here
https://github.com/mafintosh/node-modules
All contributions are welcome.
The ranking system is working really well as is, so we'll probably just add a
'last published' date and similar info to the results that can give you an
in
On Sep 20, 2013, at 2:35 PM, Mathias Buus Madsen 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.
Very interesting, but the first search f
>
> Very interesting, but the first search for "json parser" is for a shell
> script. :-) http://node-modules.com/search?q=json+parser
>
JSON.sh is on npm and is very popular so this is actually intended
behaviour - the other top results are actually quite good.. In my
personalized search json
That's definitely a real concern.
One idea was to calculate an activity level for all modules, and then show
it with a pixel that changes color based on how active it is. Kind of like
the 'pixels' in the Contributions box on your github
account, https://github.com/freeall.
It should be visible
11 matches
Mail list logo
