DEV Community

Cover image for How to choose the right NPM package in 4 steps πŸ“¦

How to choose the right NPM package in 4 steps πŸ“¦

Gleb Krishin on October 17, 2022

Hey, maybe you have been searching for the right library for your needs several times. In this article, I will present my algorithm to find suitabl...
Collapse
 
techtitans0101 profile image
TechTitans0101

Thanks @dealwith for such informative tips.

Open source is essential for application developers. It is unfortunate that Open Base has shut down. While searching for alternate, came across kandi from Open Weaver. It helps developers find code snippets, packages, libraries and solutions from millions of assets. Thanks to such tools for support to the community. Happy coding!

Collapse
 
dhruvjoshi9 profile image
Dhruv Joshi

Such a detailed and helpful blog!!! Thanks!!

Collapse
 
dealwith profile image
Gleb Krishin

Thanks for your feedback!

Collapse
 
darkwiiplayer profile image
π’ŽWii πŸ³οΈβ€βš§οΈ • Edited

How to choose the right NPM package in the real world πŸ“¦ πŸ•š πŸ˜“

This one looks good 😀

πŸ˜‚

Collapse
 
dealwith profile image
Gleb Krishin

Ahahah, yeah funny)

Collapse
 
kelh93 profile image
Ryan.ke

Helpful, Thanks

Collapse
 
dealwith profile image
Gleb Krishin

No problem!

Collapse
 
dmitriyone profile image
Dmitriy Fenko

Great moments. Thanks

Collapse
 
stefan_n profile image
Stefan Niederhauser

Awesome article, Gleb. I wish we had such a comparison table a while ago when selecting an i18n package specifically for Next.js. Might make a nice side-project to automatically display this data in a tiny overview. Something like npmcompare.com/compare/@lingui/rea..., but this is too bloated imho - and misses bundle size, which was critical in our case.

Collapse
 
dealwith profile image
Gleb Krishin

Agree, it's an excellent idea to have an open source that will generate the data like in the article plus to take something from the sources like npm compare

Collapse
 
e78230c36501509 profile image
cwtuan

The link is broken. Use npm-compare.com/@lingui/react,i18n... instead