Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
010001111354522dLooking closer at the library before using it. Check Awesome-Lists
In the case of most NPM modules, take a glimps inside the code.
Voxera844122dFirst, is it a stable library that is well used and supported or does it match your use case perfectly.
I would never use a library I would have to modify since that would make upgrading impossible.
Incase I need more control I rather use smaller libs than one big one.
dder216222dAlso if you thing “it would be cool if that lib could do that as well” put that as an issue to the repo. Guy may want help to implement, which you could then do, or tell you: “idiot, rtfm, here the oneliner”
either way a wain imo
saucyatom108821d1. Check the license.
2. Is it stable and supported? (aka not last updated 10 years ago with 100 open issues)
3. Does it cover the use-case perfectly?
4. Does the code seem sane or does it smell?
5. Is it worth it (to add this dependency), or can I make it myself in a better way within [reasonably short time]?