Is there a tool that helps compare npm downloads for a package to see what percentage of downloads are on various major versions?
Also posted to Bluesky.
13 replies
like this? majors.nullvoxpopuli.com/q?minors=fal...
Beautiful, yes! Thank you!
On closer inspection I have more questions! 😅
If a package has a v1, stable with no updates; then v2 ships ~40 patch versions, wouldn’t that bias cumulative counts to v2? A project using v2 could download up to 40 different versions but a project using v1 would have 1!
hm, not sure I follow - how does the number of versions a project _could_ download influence the cumulative number of downloads for that major?
thinking about this a bit more — limiting the results to the most recent 7 day window mitigates most of my concerns (I think!). But without that recency I would assume that a package with more versions will see more cumulative downloads over time
NpmBurst by @craigory.dev is great for this!
oooh I love a good pie chart
I really believe a sunburst is the ideal diagram for this
Oh! Neat, I wasn't sure this had gained any traction outside of my colleagues
The only problem I have is that on mobile I can't change the package, I have to change the package name via the query param.
Is that just me.?Oh, interesting 🤔. I'll throw a fix up
@reinhold.is should be fixed now. It only listened to enter keypress there.
Jeppe Reinhold was kind enough to share this tool from Craigory Coppola to compare popularity of different Major/Minor versions of a package on npm: