A small disclaimer: in this article I’m going to cover mostly translation staff. Let’s start with creating a primitive application based on Express.js by using an express-generator to scaffold it. In this particular article, we are going to cover i18next library which enables Node.js i18n. Therefore, Node.js i18n simply means Node.js internationalization. For this reason, often programming libraries to keep names short use this abbreviation. If you are wondering what i18n is about it’s just an abbreviation of the word “internationalization”. JavaScript also doesn’t stand still, and new, more modern specifications of the scripting language appear. Notable examples are TypeScript and CoffeeScript. As JavaScript has some shortcomings popularized by many online meme pictures, several such languages appear. That’s why many services are now using JavaScript or languages that are transcompiled into JavaScript as a backend language. Traditionally JavaScript was evolving as an in-browser language and Node.js opened a broad range of other valuable applications. Node.js is a popular cross-platform open-source JavaScript runtime environment. That’s why even if you not planning to support a multi-language interface right now, it is a good idea to know how you can quickly create a localization solution with Node.js i18n libraries. Therefore, if you start developing your app with localization in mind, it dramatically reduces potential pain. It turns out that one of the most productive sources of new users is localization of your app. When you have a successful application sooner or later, you need to find new sources of growth.
0 kommentar(er)
