On npmjs.org it gives the correct username, but when I run `npm info` on it I get the old one, which I'm guessing is where nodezoo gets its info. Also when I run `npm owner ls` I do get the updated username and the old one is not there.
Strange, this might be an error with npm not updating a document in the database if a new version hasn't been pushed since the owners were changed. http://nodezoo.com/#q=kat https://npmjs.org/package/kat On Tue, Nov 27, 2012 at 6:15 AM, Richard Rodger <[email protected] > wrote: > Thanks Roly - will use this in testing! > I get the data direct from npmjs.org - could you check there to see if > the older username is there too? > R. > > > On Tuesday, November 27, 2012 5:09:29 AM UTC, Roly Fentanes wrote: >> >> Awesome. Are the modules cached? I noticed that some of my older modules >> are using my older username. Also curious as how the ranking works, as I >> see some modules show up higher on the list than other modules that are >> objectively better and have been updated more recently and with more Github >> stars. >> >> ie the following show in this order when searching "youtube". But should >> show up in reverse. >> >> https://github.com/m16a1/**youtube-js<https://github.com/m16a1/youtube-js> >> https://github.com/clonn/ydl >> https://github.com/fent/node-**ytdl <https://github.com/fent/node-ytdl> >> >> >> On Monday, November 26, 2012 6:01:53 PM UTC-7, Richard Rodger wrote: >>> >>> Hi All, >>> >>> http://nodezoo.com is a search engine for modules - please give it a >>> spin and let me know what you think. >>> >>> The idea is to be able to quickly compare modules to find the best one >>> for your needs. I'll be adding in more meta data over the next few days, >>> but feel free to suggest things - e.g. Github stars. >>> >>> The ranking algorithm is based on the number of dependencies. Modules >>> used by many other modules rank higher. There are other factors, like how >>> recently the module was updated. This is a work in progress. >>> >>> >>> nodezoo is a module itself, so you can >>> npm install nodezoo >>> >>> and then run it from the command line, or even: require('nodezoo'). >>> >>> >>> The search index is elasticsearch (yes, I know, Java). Everything else >>> is Node. Still working on continuous updates from the npm changes feed. >>> >>> have fun, >>> Richard >>> >>> >>> >>> >> > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Roly Fentanes Software Engineer POP•TIP 36 Cooper Sq. 6th Floor | New York, NY 10003 m: 480.200.3369 | poptip.com <http://bit.ly/poptipemailsig> | @roly426<http://twitter.com/roly426> -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
