You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is important information when deciding between packages, it would be great to have it visible next to the package. I'm happy to try a PR for this (though I would need some support as loading this data from npm whenever benchmarks are run is a bigger change to the existing structure).
The text was updated successfully, but these errors were encountered:
I have a better idea.
Make the name of the libraries not text, but links to npm or the official website.
Thus, we will not need to make requests to npm, and who wants to, will look at all the information (issues, stars, downloading) on their own
That wouldn't be that helpful. It's easier to then open up npm-stat.com and copy paste the library names. The benefit of showing it on this page is that you can see all of the packages by all the stats and decide on the best combination of performance and expected maintenance.
This is important information when deciding between packages, it would be great to have it visible next to the package. I'm happy to try a PR for this (though I would need some support as loading this data from npm whenever benchmarks are run is a bigger change to the existing structure).
The text was updated successfully, but these errors were encountered: