Files
editor/package.json
T
dependabot[bot] 38c7a70a9f chore(deps): Bump i18next from 26.1.0 to 26.2.0 (#1893)
Bumps [i18next](https://github.com/i18next/i18next) from 26.1.0 to
26.2.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/releases">i18next's
releases</a>.</em></p>
<blockquote>
<h2>v26.2.0</h2>
<ul>
<li>feat(types): new <code>parseInterpolation</code> TypeOption (default
<code>true</code>). When set to <code>false</code> in
<code>CustomTypeOptions</code>, the type-level extractor stops parsing
translation strings for <code>{{variable}}</code> patterns. Required by
<code>i18next-icu</code> users — the default extractor mistakes ICU
MessageFormat nested-brace plurals like <code>{count, plural, one
{{count} row} other {{count} rows}}</code> for an interpolation block
and demands a phantom variable name. The flag is type-only; runtime
interpolation is governed by <code>InterpolationOptions</code> and is
unaffected. Fixes <a
href="https://redirect.github.com/i18next/i18next-icu/issues/85">i18next-icu#85</a>.</li>
<li>fix(types): expose <code>enableSelector</code> on
<code>InitOptions</code> so <code>i18next.init({ enableSelector:
'strict' })</code> typechecks without a module augmentation. The runtime
already reads <code>opts?.enableSelector</code> from init options; this
lands the matching type declaration next to the other
selector-resolution knobs. Accepts <code>false | true | 'optimize' |
'strict'</code>. Thanks <a
href="https://github.com/Faithfinder"><code>@​Faithfinder</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2431">#2431</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/blob/master/CHANGELOG.md">i18next's
changelog</a>.</em></p>
<blockquote>
<h2>26.2.0</h2>
<ul>
<li>feat(types): new <code>parseInterpolation</code> TypeOption (default
<code>true</code>). When set to <code>false</code> in
<code>CustomTypeOptions</code>, the type-level extractor stops parsing
translation strings for <code>{{variable}}</code> patterns. Required by
<code>i18next-icu</code> users — the default extractor mistakes ICU
MessageFormat nested-brace plurals like <code>{count, plural, one
{{count} row} other {{count} rows}}</code> for an interpolation block
and demands a phantom variable name. The flag is type-only; runtime
interpolation is governed by <code>InterpolationOptions</code> and is
unaffected. Fixes <a
href="https://redirect.github.com/i18next/i18next-icu/issues/85">i18next-icu#85</a>.</li>
<li>fix(types): expose <code>enableSelector</code> on
<code>InitOptions</code> so <code>i18next.init({ enableSelector:
'strict' })</code> typechecks without a module augmentation. The runtime
already reads <code>opts?.enableSelector</code> from init options; this
lands the matching type declaration next to the other
selector-resolution knobs. Accepts <code>false | true | 'optimize' |
'strict'</code>. Thanks <a
href="https://github.com/Faithfinder"><code>@​Faithfinder</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2431">#2431</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/i18next/i18next/commit/22fb6ad013c9c069c33086eb3737b4371936d5ce"><code>22fb6ad</code></a>
26.2.0</li>
<li><a
href="https://github.com/i18next/i18next/commit/b640ac41acba1145d2e9e3ed38280dc82b67cc39"><code>b640ac4</code></a>
feat(types): parseInterpolation flag for ICU-friendly t() typing
(i18next-icu...</li>
<li><a
href="https://github.com/i18next/i18next/commit/0b9debd0f72d30905371e65c02e5a9df5db78e56"><code>0b9debd</code></a>
changelog: 26.1.1 entry for <a
href="https://redirect.github.com/i18next/i18next/issues/2431">#2431</a></li>
<li><a
href="https://github.com/i18next/i18next/commit/50509e4c916c44996e23f01e7bfbceda79b62870"><code>50509e4</code></a>
fix(types): expose enableSelector on InitOptions (<a
href="https://redirect.github.com/i18next/i18next/issues/2431">#2431</a>)</li>
<li><a
href="https://github.com/i18next/i18next/commit/80b540291cf86d5be6a5bd959db82043b643bb19"><code>80b5402</code></a>
Enhance Pro Tip in README with i18next-locize-backend plugin link</li>
<li>See full diff in <a
href="https://github.com/i18next/i18next/compare/v26.1.0...v26.2.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=i18next&package-manager=npm_and_yarn&previous-version=26.1.0&new-version=26.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-05-18 23:40:26 +00:00

4.9 KiB