Deps: Bump i18next-cli from 1.65.0 to 1.67.3

[dependabot]

Bumps i18next-cli from 1.65.0 to 1.67.3.

Changelog

Sourced from i18next-cli's changelog.

1.67.3

• feat(lint): new opt-in lint.checkPunctuationConcatenation flags punctuation glued onto a translation, e.g. <label><Trans>Email</Trans>:</label> or <div>- <Trans>item</Trans></div>. Punctuation spacing and form differ across languages (French needs a narrow no-break space before :, CJK uses fullwidth ：, RTL reorders), so it belongs inside the translation or in semantic markup. Accepts the same values as checkConcatenation ('warn' / 'error' / 'off' / boolean) and defaults to 'off', since keeping punctuation out of a translation is often deliberate. Individual occurrences can be suppressed with the i18next-instrument-ignore directive (#275).

1.67.2

• fix(lint): broaden the checkConcatenation JSX detection to flag any ≥2 adjacent translation units rendered as direct siblings — a <Trans> component or a {t(...)} expression. This now catches <Trans>…</Trans>{t('…')}, {t('a')}{t('b')} and two <Trans> separated only by whitespace, in addition to the previous "<Trans> … text … <Trans>" case. Single translations next to plain literal text or punctuation are still not flagged (#275).

1.67.1

• feat(lint): lint.checkConcatenation now accepts a severity level in addition to a boolean: 'error' reports concatenation issues as errors so the lint command exits non-zero (fails CI), 'warn' (or true, the default) reports them as non-failing warnings, and 'off' (or false) 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 flag t() used only as a nested call argument (e.g. arr.indexOf(t('x')) + 1) or concatenation inside t() arguments (e.g. t('prefix.' + suffix)). Enabled by default; disable with lint.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 (the lint command 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 set severity on the issues they emit (defaults to 'error' when omitted).

... (truncated)

Commits

• 3033941 1.67.3
• 8c11594 feat(lint): opt-in checkPunctuationConcatenation (#275)
• aea509c 1.67.2
• d86cb6f fix(lint): flag >=2 adjacent translation units in JSX concatenation (#275)
• 15a7577 1.67.1
• ca015bb feat(lint): allow lint.checkConcatenation to set severity (error/warn/off) (#...
• c5a699d 1.67.0
• 7a63d39 feat(lint): warn on string concatenation in translations (#275)
• 34f2b96 1.66.2
• 6761334 fix(extract): skip empty Trans component keys (#274)
• Additional commits viewable in compare view

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA fc153f0.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

OpenSSF Scorecard

Package	Version	Score	Details
npm/i18next-cli	1.67.3	Unknown	Unknown

Scanned Files

• package-lock.json