chore(deps-dev): bump i18next-cli from 1.67.8 to 1.69.0 in the frontend group across 1 directory

[dependabot]

Bumps the frontend group with 1 update in the / directory: i18next-cli.

Updates i18next-cli from 1.67.8 to 1.69.0

Changelog

Sourced from i18next-cli's changelog.

1.69.0

• feat(lint): support acceptedTags: 'all' to lint every JSX tag, including custom components, instead of the recommended built-in tag list. Useful together with acceptedAttributes in codebases with many custom JSX elements where maintaining an explicit tag accept-list is impractical. ignoredTags and transComponents still take precedence, and the default behavior when acceptedTags is unset is unchanged (#282).

1.68.0

• feat(status): add --unused to report only unused translation keys — keys present in the translation files but no longer used in the source code. "Unused" is defined as what extract with removeUnusedKeys would delete: the report runs the extractor in dry-run mode (with removeUnusedKeys forced on, regardless of the config) and diffs the existing key set against the pruned result, so it inherits all of extract's edge-case handling (plural variants, context variants, preservePatterns, ignoreNamespaces). The command never modifies any files and exits with a non-zero status code when unused keys are found (or when source files failed to parse, since that could cause false positives), making it a dedicated CI check alongside the missing-translations check status <locale>. Combines with the locale argument and --namespace, e.g. i18next-cli status en --unused. Note that static analysis cannot detect dynamically constructed keys; to find keys that are truly unused at runtime, see https://www.locize.com/docs/guides/find-unused-translations (#281).

1.67.9

• fix(types): derive defaultNS from the generated resources when extract.defaultNS is false. i18next's type system cannot express defaultNS: false — DefaultNamespace = TypeOptions['defaultNS'] feeds Ns extends Namespace, so emitting false made every t() call silently accept any string and the generated definitions checked nothing. The namespace is now taken from the keys of the generated Resources interface (deduplicated and sorted, preferring 'translation', and preferring a namespace inside types.basePath over one resolved outside of it), with a warning naming the pick. false is still emitted when the resource files are named after locales (en.json + de.json), where deriving would turn sibling languages into namespaces. Only affects i18next.d.ts on first creation; resources.d.ts and --ci behavior are unchanged (#280).

Commits

• eacc2be 1.69.0
• 28caa1b feat(lint): support acceptedTags: 'all' to lint every tag including custom co...
• 4c61b53 fix(test): make the status --unused read-only assertion pass on Windows
• 0962adb 1.68.0
• 7295a41 feat(status): add --unused to report only unused translation keys (#281)
• 0070803 1.67.9
• 4540650 fix(types): harden defaultNS derivation when extract.defaultNS is false
• e42bdaf fix(types): derive defaultNS from generated resources when extract.defaultNS ...
• See full diff in compare view

---

Note

Low Risk
Lockfile-only dev-tool upgrade with no runtime or config edits; possible minor impact only if i18next type generation is run with defaultNS: false.

Overview
Bumps the dev dependency i18next-cli from 1.67.8 to 1.69.0 in package-lock.json only; no application or i18next.config.mjs changes.

The newer CLI adds optional capabilities (e.g. status --unused for unused keys, acceptedTags: 'all' for lint) and includes a 1.67.9 types fix when extract.defaultNS is false—which matches this repo’s extract config and only matters if generated i18next.d.ts is created or regenerated. Existing npm run i18n:extract behavior is unchanged unless you adopt the new flags or lint options.

^{Reviewed by Cursor Bugbot for commit d559fb5. Bugbot is set up for automated code reviews on this repo. Configure here.}