Love your idea. I always visit a few websites and sort of compile this data myself when looking for a library.
In my opinion 2 most important things:
I) Add autosuggestion as you have planned and do the autosuggestions RIGHT. I don't mean any fancy AI model, just autosuggestion of the most POPULAR ALTERNATIVES. That's whats missing for me in npmtrends and would be a good reason on itself for me to switch to JsDiff.
Because the biggest issue with npm is there are hundreds of libraries named reasonably yet being not used at all or just being complete bullcrap...
II) You should prioritize like this: |accuracy of data| = |UX| > |number of data sources compiled on the website|.
It's a 'at one glance' tool. I'd say it can really only by done by trial and error (or surveys...).
The metrics I find the most important are:
1) npm downloads (that you have) - social proof
2) github stars (must be somewhere at the top!) - social proof
3) date of recent commit - is the project maintained
4) number of contributors - will the project be maintained, is there a community or is it a one-man band's work
5) features - not something you can put on a chart though ;-)
6) variety of metrics: issues, issues resolved ratio, date created, size, commits/PRs trends (how actively does a project grow, it's actually missing from npmtrends),
As to what you already have:
Your NPM downloads chart reads wrong. At the beginning / in the middle of a month, like now, the trend always goes downhill. Either make it a 7week average, 30days rolling or extrapolate the December based on the downloads in this month (usually shown as a dotted line)
You need to ditch the gray color and use the colors you assigned to search results consistently.
Bundlephobia chart is wrong. Min+Gzip must be at the base of charts otherwise one does not know how to read the chart. I'm not convinced as to cumulative character of this chart either.
Google trends are not useful as they come. Hard to see what's going on with all these peeks and lows. They might be useful if you show an average of sort or a cumulative value. You'd have to look into that.
Obviously some users' score would be great but there simply is no good source of such data... maybe an average of different sources or displaying'em all could work.
PR chart -> logically, PR closed have to be at the base, not at the top
Damn, I am so opinionated ;-)
I've added it to bookmarks, though, and keep fingers crossed for you making a great tool! :-)
@zarehba
I love your thoughtful feedback and very-very much grateful to you for that! 🙏
Agree with everything!
NPM downloads. Confirming the problem 👍 Noted it down.
not sure I understand the idea with ditching the gray color. Can you elaborate?
Bundlephobia. I already had a conversation about it on reddit and I agree that gzip and non-gzip should not be stackable 👍 Will fix it.
Google Trends... It's tough. I agree, I also think that for most npm packages it doesn't make any sense. Take for example table package. What will the chart show for the keyword table? I guess it won't reflect trends for the table package 😃 So it needs some thoughts how to improve it. I think the problem with peeks and lows exists mostly in case of not very popular packages. Popular packages should have more stable graphs. Unfortunately Google Trends doesn't provide a real API to adjust the data, so my abilities are also limited here. Anyway, I'll definitely think about what I can improve
PR chart. I think it doesn't say much in its current state (for example a number of closed or merged PRs) 😃. The chart should be improved to have real value.
Thanks a lot for your other notes about metrics and their priority.
Very much valuable feedback 👍 I'll come back to it and make sure I haven't missed anything.
About the gray color - the website would be easier to read when, say, in your example, the bars pertaining to angular would be red on every chart, react ones purple etc.
Yeah, I feel your pain about Google Trends..
Keep up the good work ;-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Love your idea. I always visit a few websites and sort of compile this data myself when looking for a library.
In my opinion 2 most important things:
I) Add autosuggestion as you have planned and do the autosuggestions RIGHT. I don't mean any fancy AI model, just autosuggestion of the most POPULAR ALTERNATIVES. That's whats missing for me in npmtrends and would be a good reason on itself for me to switch to JsDiff.
Because the biggest issue with npm is there are hundreds of libraries named reasonably yet being not used at all or just being complete bullcrap...
II) You should prioritize like this: |accuracy of data| = |UX| > |number of data sources compiled on the website|.
It's a 'at one glance' tool. I'd say it can really only by done by trial and error (or surveys...).
The metrics I find the most important are:
1) npm downloads (that you have) - social proof
2) github stars (must be somewhere at the top!) - social proof
3) date of recent commit - is the project maintained
4) number of contributors - will the project be maintained, is there a community or is it a one-man band's work
5) features - not something you can put on a chart though ;-)
6) variety of metrics: issues, issues resolved ratio, date created, size, commits/PRs trends (how actively does a project grow, it's actually missing from npmtrends),
As to what you already have:
Damn, I am so opinionated ;-)
I've added it to bookmarks, though, and keep fingers crossed for you making a great tool! :-)
@zarehba I love your thoughtful feedback and very-very much grateful to you for that! 🙏
Agree with everything!
tablepackage. What will the chart show for the keywordtable? I guess it won't reflect trends for thetablepackage 😃 So it needs some thoughts how to improve it. I think the problem with peeks and lows exists mostly in case of not very popular packages. Popular packages should have more stable graphs. Unfortunately Google Trends doesn't provide a real API to adjust the data, so my abilities are also limited here. Anyway, I'll definitely think about what I can improveThanks a lot for your other notes about metrics and their priority.
Very much valuable feedback 👍 I'll come back to it and make sure I haven't missed anything.
About the gray color - the website would be easier to read when, say, in your example, the bars pertaining to angular would be red on every chart, react ones purple etc.
Yeah, I feel your pain about Google Trends..
Keep up the good work ;-)