Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
i18n-nodejs
Advanced tools
I18n module for node, out of frustration with over complicated modules for translation & localization I created this module with simplicity in mind.
npm install i18n-nodejs --save
var config = {
"lang": "ar",
"langFile": "./../../locale.json"//relative path to index.js file of i18n-nodejs module
}
//init internationalization / localization class
var i18n = require('i18n-nodejs')(config.lang, config.langFile);
console.log(i18n.__('Welcome')); // output => 'اهلا'
langFile
is JSON file have the text that you need to translate as key
and the value
is object its key
is language abbreviation and the value
is the translated text.
{
"Welcome": {
"ar": "مرحبا",
"fr": "Bienvenue"
},
"Looking for user": {
"ar": "نبحث الان عن مستخدم اخر"
},
"You have disconnected.": {
"ar": "تم قطع الاتصال."
},
"Chat": {
"ar": "شات"
}
}
The module will try to find the translation using the language abbreviation if could not find it will return the original text.
If the text has variable
that need to be translated you should add the the text like {{name}}
and you need to pass the translated value of that variable
as second arg into the __()
function.
//Language file
{
"Welcome {{name}}": {
"ar": "مرحبا {{name}}"
},
"eslam": {
"ar": "اسلام"
}
}
//index.js file
var config = {
"lang": "ar",
"langFile": "./../../locale.json"//relative path to index.js file of i18n-nodejs module
}
//init internationalization / localization class
var i18n = require('i18n-nodejs')(config.lang, config.langFile);
console.log(i18n.__("Welcome {{name}}", {name: "اسلام"}));
// output => 'مرحبا اسلام'
If you do not want to write the tranlation directly in your code (wich you should not do) you should add the value and its translation the langauage file and use it like that
console.log(i18n.__("Welcome {{name}}", {name: i18n.__("eslam")}));
// output => 'مرحبا اسلام'
Starting form version 2.0.0
we now support pluralization, First let us describe the problem let say we want to display "Hi Eslam, you have 555 points", but if you want to display that text in arabic the word "points" will have 5 different possibilities to be rendered in as it is the rule in Arabic language in case of plural each of them depend on the number before the word.
So instesd of writing it as
//this is worng
"Hi {{name}}, you have {{points_count}} points"
You should pass the count to the variable as {{var||var_count}}
i18n.__(
"Hi {{name}}, you have {{points_count}} {{points||points_count}}", {
name: i18n.__("eslam"),
points_count: 555
}
As you see we passed the variable name
aslo we passed the points_count
in two places
||
The translation file should be
{
"Hello {{name}}, you have {{points_count}} {{points||points_count}}": {
"ar": "مرحبا {{name}}, لديك {{points_count}} {{points||points_count}}"
},
"eslam": {
"ar": "اسلام"
},
"points": {
"ar": {
"0": "نقاط",
"1": "نقطة",
"2": "نقطتين",
"3": "نقاط",
"4": "نقطة",
"5": "نقطة"
}
}
}
You can find all the rules in this localization guide
There is a note also as you can see we did not submit the points
variable in the values object as second param for __(string, values object)
because now the module is smarter and will look first for the translation in the values param then if it is not there will look for it in the file set in the constructor
-Version 2.0.0 support pluralization, remove the dependency to other packages to make it even simpler and light for your app and if you passed any values for any variable in the second param it will overwrite the original value in the translation file.
FAQs
Internationalization localization package
We found that i18n-nodejs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.