i18next
i18next internationalization framework
About
i18next internationalization framework
Live mirror of the GitHub README. Updated whenever the repo's default branch changes.
i18next: learn once - translate everywhere 
i18next is a very popular internationalization framework for browser or any other javascript environment (eg. Node.js, Deno).
i18next provides:
- Flexible connection to backend (loading translations via xhr, ...)
- Optional caching, user language detection, ...
- Proper pluralizations
- Translation context
- Nesting, Variable replacement
- Flexibility: Use it everywhere
- Extensibility: eg. sprintf
- ...
Pro Tip: Looking for a way to manage your translations? Locize is the official service by i18next's creators and now offers a Free plan for small projects.
For more information visit the website:
Our focus is providing the core to building a booming ecosystem. Independent of the building blocks you choose, be it react, angular or even good old jquery proper translation capabilities are just one step away.
Documentation
The general i18next documentation is published on www.i18next.com and PR changes can be supplied here.
The react specific documentation is published on react.i18next.com and PR changes can be supplied here.
Gold Sponsors
From the creators of i18next: localization as a service - Locize
A translation management system built around the i18next ecosystem - Locize.
Now with a Free plan for small projects! Perfect for hobbyists or getting started.
With using Locize you directly support the future of i18next.
Quick facts
npm install i18nextCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
How Sourcemap Explorer detects i18next
We catch i18next from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/i18next/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/i18next/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/i18next/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/i18next/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
FAQ
What is i18next used for?
i18next internationalization framework
How can I tell if a website is using i18next?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `i18next` from two complementary signals: `node_modules/i18next/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
What is the latest version of i18next?
26.0.10, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Where can I read more?
Project homepage: https://www.i18next.com. Source code: https://github.com/i18next/i18next. Published on npm: https://www.npmjs.com/package/i18next. Licensed as MIT.
Keep reading on Sourcemap Explorer
Practical guides
Detection deep dives
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for i18next and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.