i18next - npm Package Versions

1.3.3

• optional return an objectTree from translation
• use jquery promises or callback in initialisation
• rewrote all tests with mocha.js

1.3.2

• options to init i18next sync (options -> getAsync = false)
• replace all occurence of replacement string

1.3.1

• pass options to selector.i18n() thanks to @hugojosefson
• close [issue #8(https://github.com/jamuhl/i18next/issues/8)]: Fail silently when trying to access a path with children
• cleanup
• debug flag (options.debug -> write infos/errors to console)

1.2.5

• fix for IE8

1.2.4

• added indexOf for non ECMA-262 standard compliant browsers (IE < 9)
• calling i28n() on element with data-i18n attribute will localize it now (i18n now not only works on container elements child)

1.2.3

• extended detectLng: switch via qs setLng= or cookie i18next
• assert county in locale will be uppercased en-us -> en-US
• provide option to have locale always lowercased option lowerCaseLng
• set lng cookie when set in init function

1.2

• support for translation context
• fixed zero count in plurals
• init without options, callback

1.1

• support for multiple plural forms
• common.js enabled (for node.js serverside)
• changes to be less dependent on jquery (override it's functions, add to root if no jquery)
• enable it on serverside with node.js i18next-node

1.0

• support for other attribute translation via data-i18n attribute
• bug fixes
• tests with qunit and sinon

0.9

• multi-namespace support
• loading static files or dynamic route
• jquery function for data-i18n attibute
• post missing translations to the server
• graceful fallback en-US -> en -> fallbackLng
• localstorage support
• support for pluralized strings
• insertion of variables into translations
• translation nesting

21.2.2

• log error if Intl.PluralRules API is not available

21.2.1

• do skip natural language detection, if user provided keySeparator option is passed 1670

21.2.0

• provide bundled esm distributable 1667