chore(deps-dev): Bump i18next-cli from 1.53.2 to 1.56.12

[dependabot]

Bumps i18next-cli from 1.53.2 to 1.56.12.

Changelog

Sourced from i18next-cli's changelog.

1.56.12

• feat: types.enableSelector now accepts 'strict', mirroring i18next's runtime enableSelector: 'strict' (≥ 26.1.0). When set, the extractor applies the leading-namespace rewrite uniformly: a selector path's first segment matching any namespace in the hook's scope — primary or secondary, single- or multi-ns — is rewritten to ns:rest so the key routes to the right namespace file. Same applies to useTranslation('only') paths written as $.only.foo (strict-mode shape). Generated i18next.d.ts emits enableSelector: "strict" accordingly.

1.56.11 - 2026-05-07

• extract and status now mirror i18next's runtime selector rule (v25.8.19) for multi-namespace useTranslation([nsA, nsB, ...]) hooks. When a selector path's first segment matches a secondary namespace from the hook's array, the key is routed to that namespace's file instead of the primary. Single-namespace hooks and primary-prefixed paths are unaffected — the primary namespace is never rewritten, matching i18next/src/selector.js exactly. Fixes #256.

1.56.10 - 2026-05-06

• lint now sets type: 'hardcoded' on hardcoded-string issues. The LintIssue type already declared a 'hardcoded' | 'interpolation' union, but findHardcodedStrings only emitted text and line, leaving type undefined. Consumers (including lintOnResult plugins) had to rely on type !== 'interpolation', which would silently misclassify any future issue category. The discriminant is now populated so issue.type === 'hardcoded' works as advertised. Fixes #255.

1.56.9 - 2026-04-29

• extract now propagates namespace/keyPrefix from a useTranslationNames-listed call when its result is stored on a class field and later destructured inside a method, e.g. #ctx = getTranslationContext('settings') followed by const { t } = this.#ctx (or this.#ctx()) inside a class method. Previously, only top-level VariableDeclarator initializers were tracked, so t('hello') reached through this.#ctx was extracted without its namespace. The scope manager now keeps a per-class field registry (public and private fields, including the () invocation form) and resolves this.<field> references against it during destructuring. The non-class form const { t } = getTranslationContext(...) is unchanged. Fixes #251.

1.56.8 - 2026-04-29

... (truncated)

Commits

• 6f33f56 1.56.12
• 70d808e feat: types.enableSelector: 'strict' — uniform leading-ns rewrite in extracto...
• 3224d88 1.56.11
• 8e5ebdb changelog fix
• 9fa173f extract/status: route selector secondary-ns prefix in useTranslation([nsA,nsB...
• 149893d 1.56.10
• 6d74070 populate type: 'hardcoded' on hardcoded-string lint issues (fixes #255)
• ed16625 Modernize locize.com URLs and refresh UTM tags
• 7c7c3d6 1.56.9
• 36d257f propagate namespace through class field initializers (fixes #251)
• Additional commits viewable in compare view

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.45%. Comparing base (47a42b3) to head (3bb9c2f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1884   +/-   ##
=======================================
  Coverage   46.45%   46.45%           
=======================================
  Files           3        3           
  Lines         127      127           
  Branches       35       35           
=======================================
  Hits           59       59           
  Misses         55       55           
  Partials       13       13           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[HarelM]

@dependabot recreate