Sourced from i18next-cli's changelog.
1.67.1
- feat(lint):
lint.checkConcatenationnow accepts a severity level in addition to a boolean:'error'reports concatenation issues as errors so thelintcommand exits non-zero (fails CI),'warn'(ortrue, the default) reports them as non-failing warnings, and'off'(orfalse) disables the check. Previously the concatenation check could only warn; making it fail the build required a custom plugin (#275).1.67.0
- feat(lint): detect string concatenation involving translated strings, an i18n anti-pattern that breaks in languages which reorder or inflect the pieces. The linter now flags JavaScript concatenation where an operand is a
t()call (e.g.t('greeting') + ', ' + name) and sentences split across multiple<Trans>components joined by literal text (e.g.<p><Trans>…</Trans> and <Trans>…</Trans></p>). It deliberately does not flagt()used only as a nested call argument (e.g.arr.indexOf(t('x')) + 1) or concatenation insidet()arguments (e.g.t('prefix.' + suffix)). Enabled by default; disable withlint.checkConcatenation: false(#275).- feat(lint): lint issues now carry an optional
severity('error'|'warning'). Concatenation issues are reported as warnings — they are printed but do not fail the run (thelintcommand exits non-zero only when there are errors), so adding this check does not break existing CI pipelines. Hardcoded-string and interpolation issues remain errors. Plugins may setseverityon the issues they emit (defaults to'error'when omitted).