Am Mittwoch, den 04.04.2012, 05:44 -0700 schrieb Jeff Kunkle: > I have seen those and they're pretty good for finding good modules. I guess > I'm just hoping for something based on actual usage and not just how many > people watch or fork a project. Maybe that's a close enough substitute.
I don't think that's going to be close enough for niche projects. Also, I don't think many people unwatch things they're no longer using. However, how could what you have in mind be done? The require() function would probably have to be patched to register what modules you're using. Then, that information would have to be stored locally, aggregated over some time (maybe a week or so?), and then sent to the registry or so, maybe as soon as you use node the next time. Actually, it should be possible to reuse the "npm star" functionality for this.
signature.asc
Description: This is a digitally signed message part
