request: download counts for individual versions?

npm / download-counts

Background jobs and a minimal service for collecting and delivering download counts

329 stars 27 forks source link

request: download counts for individual versions? #6

Open hughsk opened 10 years ago

hughsk commented 10 years ago

Is this at all possible? It could be really useful for module authors, e.g. tracking adoption new module versions like so:

Thanks :)

dougwilson commented 10 years ago

I would also like this. I would like to know what versions of express people are still actively installing.

jhejderup commented 10 years ago

Just recently discussed this on Twitter with @seldo, the number of downloads for a specific version is available in the raw data logs. We just need to keep our fingers crossed that this feature will be added to the REST api.

hughsk commented 10 years ago

@jhejderup awesome, good to hear the data's there at least! Fingers crossed :)

analog-nico commented 9 years ago

I once opened basically the same issue for npm-www: https://github.com/npm/newww/issues/371 See some additional thoughts there...

aoberoi commented 9 years ago

:+1:

@jhejderup is there anything the public could do to help implement this feature?

seldo commented 9 years ago

My goodness, I am behind on notifications.

This is absolutely coming; the downloads API is 14 months old now and very out of step with the rest of our architecture, so it needs to be overhauled, put on top of postgres instead of mysql, put behind the user-ACL API so people can get stats for private modules, etc.. Per-version counts will come in that update, but don't hold your breath, as we have a bunch of other stuff to build first.

analog-nico commented 9 years ago

That's awesome news!

sheerun commented 8 years ago

Please :) We need it for Bower

erossignon commented 8 years ago

:+1:

donaldpipowitch commented 7 years ago

@seldo Would love to see this for webpack 2 beta. What is the state of this issue? It sounded like it would be solved already.

seldo commented 7 years ago

It remains something we are committed to doing, but not something we currently have the resources to work on.

donaldpipowitch commented 7 years ago

@seldo Thanks for the clarification. I misread the previous comments then.

matthewadams commented 7 years ago

I'd throw in the ability to specify semver version ranges, like 1.2.x

sheerun commented 7 years ago

@seldo Can I help somehow?

zenflow commented 6 years ago

I also am willing to help.

This information would be really useful in at least a handful of situations.

What is the minimum version of TypeScript should I be targetting? (this is what brought me here)
What is the minimum version of a peer dependency that I should support in my package?
What major versions of my package should i back-port fixes to?
Are users of my package upgrading to the latest major?

LoicPoullain commented 4 years ago

Any updates on this?