Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?


Failed to load latest commit information.
Latest commit message
Commit time

The Node.js Internationalization (i18n) Working Group


Here you can find contribution guides, discuss ideas, and find out how to join meetings. This repo also contains the source for the English Node.js API documentation as well as translated versions of the documentation. The source English content is copied on a schedule from its canonical home in the doc directory of the nodejs/node repository. The translated files are added by pull requests from our Crowdin integration.


This repository can be installed as an npm package. See guides/ for installation and usage instructions.


The Node.js i18n Working Group is dedicated to the support and improvement of both Internationalization (i18n) and Localization (l10n) within the Node.js project. This Working Group serves as a function of the Node.js Community Committee.

What we're responsible for

  • The ongoing translation of the Node.js project's textual content into every language of its users.
  • The implementation of i18n support including ECMA-402 within Node.js.
  • Ensuring Node.js is compliant with common standards such as Unicode, CLDR, and harmonized with other globalization efforts.

What i18n (Internationalization) means to us

Maintaining the ability for Node.js to effectively support the cultural & socio-linguistic preferences of all international users, through:

  • Unicode processing and related services to support text written in all human languages.
  • APIs and implementations which support the specific cultural & socio-linguistic preferences, such as localized methods for displaying dates & times.
  • The ability for Node.js and its related modules & applications to be translated into distinct human languages.

For details on these aspects, see the i18n API guide.

What l10n (Localization) means to us

  • Making the Node.js project's API documentation, site, and tutorial content available in every language.
  • Providing translators with a useful and productive platform to work in.
  • Provisioning Node.js with all l10n assets, through coordination with Node.js core contributors.

Members of this group are not responsible for performing the actual translations, but of coordinating the translation among the language-specific l10n groups.

Summary of our Responsibilities

  1. Supporting l10n groups who are actively translating the content of Node.js into their own languages.
  2. i18n support for Node.js, and its related initiatives.
  3. Ensuring i18n compliance with all relevant standards such as Unicode and ECMA-402.
  4. Continual refinement and maintenance of the i18n Working Group's processes, platform service accounts, and related module repositories & source code.

NOTE: Still confused about the "i18n" versus "l10n" distinction? Read "i18n vs l10n — what’s the diff?" article to find some answers.


There are many ways to get involved, and your help is wanted and appreciated.


Help us get Node.js translated into your native language and reach more people's hearts. Please read these guides to get started:

  • Getting started - basic understanding about the translation process
  • Roles - information about roles and hierarchy in Node.js localization process
  • Teams - explains the structure of localization teams and their goals
  • Crowdin - reviews the functionality of Crowdin which is used to translate Node.js


Help make sure Node.js applications continue to support all the world’s languages and cultures. See i18n API to get started.

Current Members

Name GitHub Twitter
Adam Miller amiller-gh millea9
Aissaoui Ahmed Aissaoui Ahmed Aissaoui Ahmed
Alexandr Tovmach alexandrtovmach alexandrtovmach
Alexey Temnykov Alex-Temny temnykov
Amor amorist amor90s
Andrew Bus iAndrewCA AndrewPaulBus
Antoine Olivier Toinane Toinane
Benjamin Zaslavsky Tiriel Ben_Tiriel
Ben Michel obensource obensource
Dhruv Jain maddhruv maddhruv
Franz de Copenhague FranzDeCopenhague FranzDeCopenhague
Ilyes Chouia Ilyes Chouia Ilyes Chouia
Jonathan Cardoso JCMais _jonathancardos
José J. Pérez Rivas JoseJPR JoseJ_PR
Laurent Goderre LaurentGoderre LaurentGoderre
Łukasz Szewczak lukaszewczak lukaszewczak
Nick Schonning nschonni nschonni
Rachel White rachelnicole ohhoe
Raja Sekar rajzshkr rajzshkr
Richard Littauer RichardLitt richlitt
Ryo Aramaki ryo-a geo_vitya
Ryuichi Okumura okuryu okuryu
Sam Yamashita sotayamashita sota0805
Steven R. Loomis srl295 srl295
Tamerlan Satualdypov onl1ner onl1ner1
Tiago Danin TiagoDanin _TiagoEDGE
Vanessa Yuen vanessayuenn vanessayuenn
Volkan Nazmi Metin Volem volemnic
Wexpo Lyu laosb it99p
Yuki Okushi JohnTitor fr4ternite
Zeke Sikelianos zeke zeke


If you're interested in joining this group or would like to leave a question or comment for its members, please create an issue or submit a pull request. Keep in mind, you don't have to be a member of this group to start translating. You can read more about contributing translations in the Getting started guide.


The Node.js Internationalization Working Group – A Community Committee initiative.




Code of conduct

Security policy





No releases published


No packages published