npm cleanup? #4753

Closed
Anachron opened this Issue Feb 22, 2014 · 12 comments

Comments

Projects
None yet
7 participants

I've been searching for npm repositories with keyword "framework" to find some new interesting NodeJS frameworks. When I did this the last time one year ago, there were a lot of newcomers and a lot of progress.

Now when I do the same today
https://www.npmjs.org/browse/keyword/framework/
I can find quite an impressive amount of those libraries being highly outdated, with 11 months until 2 years of inactivity, many (more than 50%) with invalid github links and if you do a quick research, there is either no more information about the project or canceled.

So my idea is, there are 60.000 NPM modules in total. Maybe check 10 NPM modules a minute and if there was no activity in a longer time and the github-link is invalid (check return code), is it possible to automatically clean them from npm?

I'm getting more and more depressed by how much stuff gets pushed into NPM and how less of them is actually useable.

Member

timoxley commented Feb 22, 2014

The problem of module discovery is real and well-known. Arbitrarily removing packages from npm is not a good solution imo, but npm search could definitely do with some more filtering/sorting capabilities.

+1 there are so many module names i want to use, but can't. there are also module names i own that i don't care and am too lazy to delete.

would be nice to prune packages that 1) don't have any dependents 2) inactive for X months 3) no valid homepage/github URL. send devs an email to just update the homepage/github url to not have the module be deleted.

Contributor

rlidwka commented Feb 23, 2014

there are so many module names i want to use, but can't.

Same here, but I'd rather see namespaces.

But seriously, there is something we should do.
We can't let the registry grow more and more without making sure there is quality and/or they are being updated frequently.

I have had some naming issues too, like trying to add a package with a name that already existed, which wasn't changed since 2 years and was dead in github (the author just said its uncontinued).

It's not that we need to find a solution for today, but maybe we can have a little chik-chat about it?

Contributor

evanlucas commented Feb 23, 2014

would be nice to prune packages that 1) don't have any dependents 2) inactive for X months 3) no valid homepage/github URL. send devs an email to just update the homepage/github url to not have the module be deleted.

@jonathanong part 1 would be a major problem for me... I know that we depend on packages (privately) that do not have any public dependents. Granted, most of them are currently active.

@evanlucas add a github url or homepage.

Contributor

evanlucas commented Feb 23, 2014

Ah you mean meets all 3 of those? My fault.

Sent from my iPhone

On Feb 23, 2014, at 2:30 PM, Jonathan Ong notifications@github.com wrote:

@evanlucas add a github url or homepage.


Reply to this email directly or view it on GitHub.

Meow, anyone still on this?

Contributor

guybrush commented Apr 20, 2014

please dont just "clean" random stuff on npm, at least try to contact authors before you remove anything. also after "cleaning" you cant use the version-numbers which have already been used anyway (see http://blog.npmjs.org/post/77758351673/no-more-npm-publish-f).

@othiym23 othiym23 changed the title from Discussion: NPM cleanup? to npm cleanup? Sep 26, 2014

Anachron commented Oct 7, 2014

How about this issue? I would like to know if there is any progress.

Contributor

othiym23 commented Oct 7, 2014

npm as a team has a different take on how to make it easier to discover new useful packages. Also, we do have a dispute mechanism in place, and while it's imperfect, we're improving it and it suits our needs better than dealing with the chaos of mass purges of quiescent packages.

There are many names out there, and with the advent of scopes (which will be coming to npm's public registry before the end of the year, probably), there are many more opportunities for coming up with short, pithy names coming soon. I'll leave this open as a feature request, but this isn't anything likely to be implemented soon.

Contributor

othiym23 commented Jun 22, 2016

We've since come up with a much clearer unpublish policy that pushes the primary npm registry much closer to being immutable (it took a real trial by fire for us to get there, too). That means that ideas like this are, realistically speaking, off the table now. That said, the discoverability problem is still very real, everyone at npm is dissatisfied with npm's own searching tools (although we also all seem to like https://npms.io/ until we have the time to tackle search effectively ourselves). In either case, I'm closing this feature request. Thanks to all for your time and participation!

@othiym23 othiym23 closed this Jun 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment