chore(deps-dev): bump i18next-cli from 1.51.7 to 1.58.1

[dependabot]

Bumps i18next-cli from 1.51.7 to 1.58.1.

Changelog

Sourced from i18next-cli's changelog.

1.58.1

• fix: types now accepts .yaml/.yml (and .json5) input files. The command's internal loadFile previously fell through to JSON.parse for any non-TS/JS file, so YAML/JSON5 translation sources threw a SyntaxError even though i18next-resources-for-ts supports them and yaml / @croct/json5-parser are already direct dependencies. Fixes #258.

1.58.0

• feat: extract gains a --with-types flag. When set, the TypeScript definitions are regenerated in the same process after extraction (on every re-run in --watch mode) whenever translation files actually changed. This removes the need to run extract -w and types -w as two parallel processes — which suffered from a chokidar mid-write race where the types output ended up one cycle behind the JSON files. Skipped under --dry-run (no files written) and --ci (exits before this point).
• fix: types --watch now uses chokidar's awaitWriteFinish option, so the watcher no longer triggers mid-write when another process (e.g. extract -w) is rewriting the same translation files. Hardens the existing two-process workflow for users who keep it. Fixes #257.

1.57.0

• feat: init wizard now asks "Translation backend?" with three choices — local files (default, unchanged behaviour), Locize, or other/skip. Picking Locize opens the signup page in the user's default browser, prompts for Project ID and (optional) API key, and writes a locize block into the generated config matching the shape consumed by locize-sync / locize-download / locize-migrate. Auto-translate is intentionally not written into the config — it's a Locize project setting toggled in the web UI — and the closing message points users there. No telemetry, no tracking parameters; only the existing ?from=i18next-cli+init+wizard attribution on the signup URL.

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

... (truncated)

Commits

• 6f9c3ee 1.58.1
• d0667cc fix: types command supports .yaml/.yml/.json5 input (fixes #258)
• e089749 1.58.0
• c2893be feat: extract --with-types + awaitWriteFinish on types watcher (fixes #257)
• d7ca60b 1.57.0
• 3da5391 feat: init wizard — add "Translation backend?" question with Locize option
• 3fbec8e Add Locize advice section near the top of README
• 6f33f56 1.56.12
• 70d808e feat: types.enableSelector: 'strict' — uniform leading-ns rewrite in extracto...
• 3224d88 1.56.11
• Additional commits viewable in compare view