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 suitable and share appropriate resources. For example, I will try to find a good library for front-end localisation.
I post some of them here, but it's good to have more options.
It's an obvious tip, but not everybody understands what to check. You should understand your business requirements and then go to the doc to see if the libs contain all of the features you need and support a translation format for your project.
- Try to understand who maintains the project. If even one repo is less popular, it will have a founder who understands the problems of other frameworks in the industry and solves them more efficiently.
- Check for the issues, how they are reviewed, and are the community actively collaborates to improve the package.
- Check the project insights page. It's a place where you will find more statistical data.
- If you cannot find a needed feature in the documentation, it's possible that authors forgot to add it, or didn't have enough time for it, so it's definitely best to go to the source files and check them.
It's an excellent way to structure all information into one table.
|Name||Size (minified + gzipped)||Dependecies||Typescript||Open/Closed issues||Last publish|
|react-i18next||6.7kB||2||8%||8/1044||a month ago|
|lingui||7.8kB||3||89%||20/693||4 months ago|
|react-intl||17.8kB||10||77%||12/1686||4 days ago|
|react-translated||7.8kB||2||0%||3/6||3 years ago|
In our case, for the front-end localisation lib, we will check several points:
- Is it easy to integrate into your project? Maybe your monorepo already has some localisation dependencies
- Does it support your front-end framework
- After the integration, it's good to measure performance changes
You will have a bigger picture of what is going on with your npm packages. Have fun!