Home
Starting Up
Case Studies DB
Products
Ideas DB
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Sign in
Join
4
Likes
6
Comments
I built a tool that tells you whether you should use an npm package or not
By
newtonry
June 11, 2018
Should I use this package?
More context about the factors in my blog post:
http://bit.ly/2MofOds
Very cool. This is something many of us internalize when figuring out the longevity of a package. If we could just search instead of using a link it would be even better.
Done. Just for you.
Worked for the first package I searched, nice!
I was expecting to see something more of code analysis as some packages are just 10 lines of code which you can implement in your code without requiring another dependency...
That's absolutely a factor everybody should take into consideration. I covered it a bit in my blog post http://bit.ly/2JOczgN, but haven't built anything to analyze the complexity/usefulness of the code, although that could be interesting.
This comment was deleted 7 years ago
I think you are correct. This is certainly not a science at the moment, so I'll likely do some adjusting of the weights of factors. I should probably also add a disclaimer.
At the end of the day it's about an informed choice by the user, which is why I chose to include the individual statistics. To let them make a more informed decision.
Certainly something like lodash isn't going to be fresh, as not many changes are needed. And smaller packages are always going have a riskier community. Every package starts somewhere.
This comment was deleted 7 years ago