Sourced from i18next-resources-to-backend's changelog.
1.2.2
- security: validate
languageandnamespaceinread()before they are passed to the loader. i18next resolves any string as a language unlesssupportedLngsis set, so these values can carry whatever a language detector picked up from the querystring, path or a cookie. The documented usage pattern isimport(./locales/${language}/${namespace}.json), and while a bundler compiles that template to a fixed context map, an unbundled ESM runtime (Node SSR) resolves the specifier against the filesystem, where a crafted value escapes the locales directory. Values containing..,\, control characters,__proto__/constructor/prototype, or longer than 128 characters are now rejected with an error and the loader is never called;/is rejected forlanguagebut allowed fornamespace, where nested layouts such asa/bare legitimate. The same check keeps the static-resources lookup offObject.prototype.
7992601
1.2.28b7240c
cosmetics1d45d0b
security: validate language/namespace before calling the loader75a31f8
README: mention npx i18next-cli localize as the zero-to-localized
path12858c7
Add Locize advice section near the top of READMEe3f24cd
Modernize locize.com URLs and refresh UTM tags33a1f29
chore: ignore .env*, *.pem, *.key in .gitignore