Sourced from i18next-cli's changelog.
1.87.0
- chore: depends on i18next 27 and react-i18next 18 (
^27.0.0,^18.0.0). The cli loads react-i18next only to build<Trans>keys with itsnodesToString, whose output is the same in 18, so extracted keys do not change. Projects on i18next 26 or react-i18next 17 keep working: npm installs the cli's own copies next to theirs.- fix(instrument): the generated i18next init file for i18next-fs-backend sets
initAsync: falseinstead ofinitImmediate: false, an option i18next 26 removed, so it was ignored.- fix(instrument): the comment on
returnEmptyString: falsein the generated init file said the opposite of what the option does. It now says that an empty translation falls back, which is the default since i18next 27.1.86.0
- feat: new
extract.omitMissingKeys(trueor a list of languages):extractandsyncleave keys that are missing in those secondary languages out of their files instead of writingdefaultValue(""), so i18next falls back tofallbackLngat runtime, also wherereturnEmptyString: falsecan't be set or translators treat an empty string as done. Existing translations stay, unused keys are still removed, andstatusstill counts the omitted keys as missing. (#328, thanks@​BenjaminVanRyseghem).
f843f59
1.87.09045c20
docs: changelog for 1.87.044c69e4
chore: depend on i18next 27 and react-i18next 18881547d
fix(instrument): the generated init file uses initAsync and describes
returnE...fcb5a93
test: give the git-based sync --changed-only tests 30sd025e00
1.86.0a41bf85
docs: changelog for 1.86.0bd32bb3
feat(sync): leave missing keys out for omitMissingKeys languages88a105c
feat(extract): add omitMissingKeys option for per-language fallback (#328)