npm / i18next-browser-languagedetector
i18next-browser-languagedetector
What changed in i18next-browser-languagedetector 4 to 8, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-27.
3 breaking1 behavior and defaults2 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initi18next-browser-languagedetector 83 changes
Behavior and default changes 1
Detects language tags with script and region subtags in subdomains, while continuing to ignore other subdomains such as staging and preview deployment labels.
Fixes and other changes 2
Language segments containing digits are kept intact, so
/es-419/and#/es-419detectes-419; segments starting with a digit still yield no language.Adds the missing TypeScript definition for hash options, so developers can use them with type support.
i18next-browser-languagedetector 43 changes
Breaking changes 3
Bower support was removed.
Distribution paths changed from dist/es to dist/esm and from dist/commonjs to dist/cjs; individual files became one bundled file.
The deprecated jsnext:main field was removed from package.json.