Skip to content

chore(deps-dev): bump the dev-minor group across 1 directory with 9 updates - #16

Merged
xinghe-labs merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-minor-078a9c8ced
Nov 10, 2026
Merged

xinghe-labs merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-minor-078a9c8ced

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown
Contributor

Bumps the dev-minor group with 9 updates in the / directory:

Package From To
@types/node 26.6.5 26.6.6
antd 6.6.6 6.7.0
eslint 10.13.0 10.14.0
globals 17.13.0 17.14.0
i18next 26.5.2 26.7.2
react-i18next 17.1.0 17.1.13
typescript-eslint 8.71.2 8.72.1
vitest 5.0.5 5.1.0
zustand 5.0.15 5.1.0

Updates @types/node from 26.6.5 to 26.6.6

Commits

Updates antd from 6.6.6 to 6.7.0

Release notes

Sourced from antd's releases.

6.7.0

  • 🆕 Add Button, Tag, Steps, Alert, and Timeline support for the global ConfigProvider variant, and component-specific divider.variant configuration for Divider line styles. #59589 #59588 #59578 #59577 #59587 #59576 @​QDyanbing
  • 🆕 Add suffix to DatePicker, TimePicker, Select, AutoComplete, Cascader, and TreeSelect to customize suffix content, with state-based rendering for selection components. Deprecate suffixIcon in favor of suffix while retaining compatibility. #59240 #59185 @​QDyanbing @​meet-student
  • 🆕 Add allowClear.tabIndex to Input, Input.TextArea, Mentions, InputNumber, Select, AutoComplete, TreeSelect, Cascader, DatePicker, and TimePicker to control clear-button Tab order. Add allowClear.label to Input, Input.TextArea, Mentions, DatePicker, and TimePicker for accessible clear-button names, with field-level ConfigProvider inheritance. #59566 #59567 #59548 @​QDyanbing
  • 🆕 Add App Fragment ref support with component={false} in React 19.3 and later. #59281 @​li-jia-nan
  • 🆕 Add BorderBeam items prop to configure each beam's color, lineWidth, outset, and size, with the array length determining the beam count. #59095 @​QDyanbing
  • 🆕 Add Cascader checkStrictly to select parent and child options independently in multiple mode. #59566 @​QDyanbing
  • 🆕 Add component-specific ConfigProvider allowClear settings for Cascader, TreeSelect, and AutoComplete to configure their clear buttons globally. #59593 #59592 #59591 @​QDyanbing
  • 🆕 Add Checkbox.Group and Radio.Group classNames and styles to customize group containers, items, icons, and labels. #59058 #59059 @​QDyanbing
  • 🆕 Add InputNumber allowClear and onClear to clear values with customizable icons, disabled state, and accessible labels. #59251 @​nikzanda
  • 🆕 Add Space align="stretch" to stretch child elements along the cross axis. #59005 @​dogledogle
  • 🆕 Add Typography shimmer prop for animated shimmering text, with duration configuring motion and wait times separately. #59054 @​zombieJ
  • 🛠 Align Input, Input.TextArea, Mentions, InputNumber, Select, AutoComplete, TreeSelect, Cascader, DatePicker, and TimePicker allowClear.disabled behavior so true removes the clear button consistently with allowClear={false}. #59548 #59566 #59567 @​QDyanbing
  • 💄 Replace Alert container radius component token borderRadius with containerBorderRadius; migrate custom container radius overrides to the new token. #59305 @​MadCcc
  • DatePicker
    • 🆕 Add DatePicker and TimePicker components.nowButton and components.okButton to customize Today/Now and confirmation buttons independently. Deprecate the legacy components.button while retaining compatibility. #59778 @​yoyo837
    • ⌨️ Improve DatePicker and TimePicker keyboard and screen reader support, including arrow-key navigation, Enter/Space selection, and skipping disabled time options, plus keyboard activation and native disabled states for Today/Now footer buttons. #59778 #59367 @​yoyo837
    • 🐞 Fix DatePicker and TimePicker ignoring clearIcon settings when an allowClear object omits clearIcon. #59565 @​QDyanbing
    • 🐞 Fix DatePicker, TimePicker, and Calendar dependency imports in native Node ESM environments. #59261 @​zombieJ
    • 🐞 Fix DatePicker parsing localized date input with Day.js when the component locale differs from the global locale. #59240 @​QDyanbing
    • 🌐 Correct DatePicker zh_TW week-selection terminology. #59261 @​zombieJ
  • Select
    • 🆕 Add Select autoComplete and ConfigProvider select.autoComplete to configure browser autocomplete behavior for the search input. #59566 #59632 @​QDyanbing
    • ⌨️ Improve screen reader support for Select, Cascader, TreeSelect, and AutoComplete by hiding default decorative arrow, search, and loading icons. #59709 @​droduit
    • ⌨️ Improve Select, Cascader, and TreeSelect clear-button keyboard accessibility with focus visibility, focus outlines, and localized accessible labels. #58267 @​Pareder
    • ⌨️ Fix Select and AutoComplete screen reader announcements of option positions, total counts, and groups in virtual scrolling mode. #58993 @​yoyo837
  • Table
    • 🆕 Add Table expandable.showExpandAll and expandable.onExpandAll to expand or collapse all expandable rows on the current page when using expandedRowRender. #59036 @​nikzanda
    • 🆕 Add Table components.ExpandIcon and an expandable.columnTitle render function to customize row and expand-all controls. Deprecate expandable.expandIcon in favor of components.ExpandIcon while retaining compatibility. #59036 @​nikzanda
    • ⌨️ Improve Table row selection accessibility with localized accessible names and keyboard access to custom selection menus. #58969 @​thlovey
    • ⚡️ Improve Table performance when applying multiple column filters to deeply nested data. #59719 @​Aminark
  • Tree
    • 💄 Improve Tree non-checkable selectable={false} nodes with disabled text colors and cursors, without hover highlighting. #58906 @​EmilyyyLiu
    • 🐞 Fix Tree ignoring defaults and preventing uncontrolled updates when expandedKeys, selectedKeys, and similar props are explicitly undefined. #59274 @​aojunhao123
    • 🐞 Fix Tree unexpectedly scrolling when a focusable element inside a node title receives focus. #59274 @​aojunhao123
    • 🐞 Fix Tree drop targets before nested first-child nodes, overwritten custom drag text, and delayed hover expansion after unmount. #59274 @​aojunhao123
  • Listy
    • 🆕 Add Listy rowKey callback's second argument index to generate keys from row indexes. #59347 @​aojunhao123
    • 🆕 Add Listy rowHoverable prop to disable row hover highlighting. #59273 @​QDyanbing
    • 🆕 Add Listy scrollWidth prop to enable horizontal scrolling for virtual lists wider than the container. #59197 @​aojunhao123
  • Pagination
    • 🆕 Add an optional third info argument with info.recommendPage to Pagination onChange when page size changes to help preserve the current data position, also available through Table and List pagination.onChange. #58604 @​EmilyyyLiu
    • ♿ Improve Pagination list semantics and keyboard and disabled-state accessibility for pagination controls. #58604 @​EmilyyyLiu
    • 🌐 Correct Pagination and page-size text in Armenian (hy_AM), Albanian (sq_AL), Nepali (ne_NP), and Traditional Chinese (zh_TW) locales. #59500 #59499 #58604 @​yoyo837 @​EmilyyyLiu
  • Button
    • 🐞 Fix Button ignoring tabIndex when href is set. #59732 @​nikzanda
    • 🐞 Fix Button not applying component-specific non-solid variants from ConfigProvider when color is omitted. #59589 @​QDyanbing
  • ColorPicker
    • 🆕 Add ColorPicker styles.popup.container and classNames.popup.container to customize the popup content container, and deprecate styles.popupOverlayInner while preserving compatibility until v7. #59743 @​QDyanbing
    • 🐞 Fix ColorPicker ignoring styles.popupOverlayInner when styles is a function or configured through ConfigProvider. #59743 @​QDyanbing

... (truncated)

Changelog

Sourced from antd's changelog.

6.7.0

2026-11-04

  • 🆕 Add Button, Tag, Steps, Alert, and Timeline support for the global ConfigProvider variant, and component-specific divider.variant configuration for Divider line styles. #59589 #59588 #59578 #59577 #59587 #59576 @​QDyanbing
  • 🆕 Add suffix to DatePicker, TimePicker, Select, AutoComplete, Cascader, and TreeSelect to customize suffix content, with state-based rendering for selection components. Deprecate suffixIcon in favor of suffix while retaining compatibility. #59240 #59185 @​QDyanbing @​meet-student
  • 🆕 Add allowClear.tabIndex to Input, Input.TextArea, Mentions, InputNumber, Select, AutoComplete, TreeSelect, Cascader, DatePicker, and TimePicker to control clear-button Tab order. Add allowClear.label to Input, Input.TextArea, Mentions, DatePicker, and TimePicker for accessible clear-button names, with field-level ConfigProvider inheritance. #59566 #59567 #59548 @​QDyanbing
  • 🆕 Add App Fragment ref support with component={false} in React 19.3 and later. #59281 @​li-jia-nan
  • 🆕 Add BorderBeam items prop to configure each beam's color, lineWidth, outset, and size, with the array length determining the beam count. #59095 @​QDyanbing
  • 🆕 Add Cascader checkStrictly to select parent and child options independently in multiple mode. #59566 @​QDyanbing
  • 🆕 Add component-specific ConfigProvider allowClear settings for Cascader, TreeSelect, and AutoComplete to configure their clear buttons globally. #59593 #59592 #59591 @​QDyanbing
  • 🆕 Add Checkbox.Group and Radio.Group classNames and styles to customize group containers, items, icons, and labels. #59058 #59059 @​QDyanbing
  • 🆕 Add InputNumber allowClear and onClear to clear values with customizable icons, disabled state, and accessible labels. #59251 @​nikzanda
  • 🆕 Add Space align="stretch" to stretch child elements along the cross axis. #59005 @​dogledogle
  • 🆕 Add Typography shimmer prop for animated shimmering text, with duration configuring motion and wait times separately. #59054 @​zombieJ
  • 🛠 Align Input, Input.TextArea, Mentions, InputNumber, Select, AutoComplete, TreeSelect, Cascader, DatePicker, and TimePicker allowClear.disabled behavior so true removes the clear button consistently with allowClear={false}. #59548 #59566 #59567 @​QDyanbing
  • 💄 Replace Alert container radius component token borderRadius with containerBorderRadius; migrate custom container radius overrides to the new token. #59305 @​MadCcc
  • DatePicker
    • 🆕 Add DatePicker and TimePicker components.nowButton and components.okButton to customize Today/Now and confirmation buttons independently. Deprecate the legacy components.button while retaining compatibility. #59778 @​yoyo837
    • ⌨️ Improve DatePicker and TimePicker keyboard and screen reader support, including arrow-key navigation, Enter/Space selection, and skipping disabled time options, plus keyboard activation and native disabled states for Today/Now footer buttons. #59778 #59367 @​yoyo837
    • 🐞 Fix DatePicker and TimePicker ignoring clearIcon settings when an allowClear object omits clearIcon. #59565 @​QDyanbing
    • 🐞 Fix DatePicker, TimePicker, and Calendar dependency imports in native Node ESM environments. #59261 @​zombieJ
    • 🐞 Fix DatePicker parsing localized date input with Day.js when the component locale differs from the global locale. #59240 @​QDyanbing
    • 🌐 Correct DatePicker zh_TW week-selection terminology. #59261 @​zombieJ
  • Select
    • 🆕 Add Select autoComplete and ConfigProvider select.autoComplete to configure browser autocomplete behavior for the search input. #59566 #59632 @​QDyanbing
    • ⌨️ Improve screen reader support for Select, Cascader, TreeSelect, and AutoComplete by hiding default decorative arrow, search, and loading icons. #59709 @​droduit
    • ⌨️ Improve Select, Cascader, and TreeSelect clear-button keyboard accessibility with focus visibility, focus outlines, and localized accessible labels. #58267 @​Pareder
    • ⌨️ Fix Select and AutoComplete screen reader announcements of option positions, total counts, and groups in virtual scrolling mode. #58993 @​yoyo837
  • Table
    • 🆕 Add Table expandable.showExpandAll and expandable.onExpandAll to expand or collapse all expandable rows on the current page when using expandedRowRender. #59036 @​nikzanda
    • 🆕 Add Table components.ExpandIcon and an expandable.columnTitle render function to customize row and expand-all controls. Deprecate expandable.expandIcon in favor of components.ExpandIcon while retaining compatibility. #59036 @​nikzanda
    • ⌨️ Improve Table row selection accessibility with localized accessible names and keyboard access to custom selection menus. #58969 @​thlovey
    • ⚡️ Improve Table performance when applying multiple column filters to deeply nested data. #59719 @​Aminark
  • Tree
    • 💄 Improve Tree non-checkable selectable={false} nodes with disabled text colors and cursors, without hover highlighting. #58906 @​EmilyyyLiu
    • 🐞 Fix Tree ignoring defaults and preventing uncontrolled updates when expandedKeys, selectedKeys, and similar props are explicitly undefined. #59274 @​aojunhao123
    • 🐞 Fix Tree unexpectedly scrolling when a focusable element inside a node title receives focus. #59274 @​aojunhao123
    • 🐞 Fix Tree drop targets before nested first-child nodes, overwritten custom drag text, and delayed hover expansion after unmount. #59274 @​aojunhao123
  • Listy
    • 🆕 Add Listy rowKey callback's second argument index to generate keys from row indexes. #59347 @​aojunhao123
    • 🆕 Add Listy rowHoverable prop to disable row hover highlighting. #59273 @​QDyanbing
    • 🆕 Add Listy scrollWidth prop to enable horizontal scrolling for virtual lists wider than the container. #59197 @​aojunhao123
  • Pagination
    • 🆕 Add an optional third info argument with info.recommendPage to Pagination onChange when page size changes to help preserve the current data position, also available through Table and List pagination.onChange. #58604 @​EmilyyyLiu
    • ♿ Improve Pagination list semantics and keyboard and disabled-state accessibility for pagination controls. #58604 @​EmilyyyLiu
    • 🌐 Correct Pagination and page-size text in Armenian (hy_AM), Albanian (sq_AL), Nepali (ne_NP), and Traditional Chinese (zh_TW) locales. #59500 #59499 #58604 @​yoyo837 @​EmilyyyLiu
  • Button
    • 🐞 Fix Button ignoring tabIndex when href is set. #59732 @​nikzanda
    • 🐞 Fix Button not applying component-specific non-solid variants from ConfigProvider when color is omitted. #59589 @​QDyanbing

... (truncated)

Commits

Updates eslint from 10.13.0 to 10.14.0

Release notes

Sourced from eslint's releases.

v10.14.0

Features

  • d23a7f9 feat: fix property descriptor handling in func-name-matching (#21400) (xbinaryx)

Bug Fixes

  • 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460) (lumir)
  • 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449) (xbinaryx)
  • 161558a fix: handle LS, PS and empty hashbang comments (#21419) (lumir)
  • 6194939 fix: no-invalid-this crash on accessor fields without initializer (#21442) (xbinaryx)
  • 9155e14 fix: Update @​humanfs/node dependency version (#21434) (Nicholas C. Zakas)
  • cb2b9d4 fix: avoid invalid object-shorthand fixes for super methods (#21323) (dvd233)
  • 5ee3915 fix: yoda invalid autofix at statement start (#21424) (Daniel Pinto)

Documentation

  • 0f94f47 docs: remove zh-hans from docs language switcher (#21437) (lumir)
  • dab466e docs: Update README (GitHub Actions Bot)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452) (Pixel)
  • 7697550 docs: Update README (GitHub Actions Bot)
  • 0c699d5 docs: Remove Tidelift commercial support (#21416) (Milos Djermanovic)
  • 0880666 docs: update loadESLint() documentation for v10 (#21374) (Minseon Kim)
  • e06fe87 docs: Revise AI acknowledgment options in PR template (#21414) (Nicholas C. Zakas)

Chores

  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462) (Francesco Trotta)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450) (renovate[bot])
  • a031c40 chore: update ecosystem plugins (#21445) (ESLint Bot)
  • 67d2ca2 chore: add troubleshooting page URL to circular fixes warning message (#21429) (Milos Djermanovic)
  • 276021d chore: update github/codeql-action action to v4.39.0 (#21432) (renovate[bot])
  • 449724e chore: update ecosystem plugins (#21420) (ESLint Bot)
  • 8ffeb8c chore: update dependency prettier to v3.9.10 (#21417) (renovate[bot])
Commits
  • 12cbff4 10.14.0
  • 6b696e7 Build: changelog update for 10.14.0
  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462)
  • 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460)
  • 0f94f47 docs: remove zh-hans from docs language switcher (#21437)
  • dab466e docs: Update README
  • 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450)
  • 161558a fix: handle LS, PS and empty hashbang comments (#21419)
  • Additional commits viewable in compare view

Updates globals from 17.13.0 to 17.14.0

Release notes

Sourced from globals's releases.

v17.14.0

  • Update globals (2026-11-01) (#355) 7abfb5d

sindresorhus/globals@v17.13.0...v17.14.0

Commits

Updates i18next from 26.5.2 to 26.7.2

Release notes

Sourced from i18next's releases.

v26.7.2

  • fix: the debug-mode deprecation warning for a language code without a region no longer says that v27 replaces aliases. 26.7.0 and 26.7.1 warned that v27 turns 'iw' into 'he' or 'tl' into 'fil' and asked you to rename them. v27 only gives such codes their canonical casing ('EN' becomes 'en', 'IW' becomes 'iw'), so iw, tl, eng and similar codes stay as they are. If you renamed them because of that warning, you can keep or restore the old codes. The warning now only appears when the casing changes.

v26.7.1

  • fix: reloadResources() retries the bundles that failed to load. The load queue skipped them also when reloading, so a language whose first load failed (a backend or network outage at startup) stayed missing. i18next-http-backend 4.0.8, i18next-chained-backend 5.0.7 and i18next-locize-backend 10.0.5 reload through reloadResources() with i18next 26.7, so their reloadInterval no longer recovered from such a failure, as their own reload did before.
  • fix: reloadResources() without languages reloads the current languages and every language the backend loaded or tried to load, for the instance and its clones, as the API docs describe ("pass languages and namespaces if you don't want to reload all"). It reloaded only the current languages, so on a server (one clone per request with i18next-http-middleware) a backend's reloadInterval never refreshed the languages loaded for requests. It never requests cimode. With languages given, nothing changes.

v26.7.0

The last 26.x minor before v27, which follows in about a week. It adds the APIs v27 builds on, and with debug: true it warns wherever a setup relies on something v27 changes. Most of the v27 defaults are existing options, so you can try them now:

i18next.init({
  debug: true, // prints the warnings below
  fallbackLng: 'en', // v27: fallbackLng defaults to false, set your source language (no implicit 'dev')
  returnEmptyString: false, // v27 default: an empty string falls back like a missing key
  cleanCode: true, // close to v27, which canonicalizes codes without a region ('EN' becomes 'en')
});
declare module 'i18next' {
  interface CustomTypeOptions {
    strictInterpolationChecks: true; // v27 default
    returnEmptyString: false; // v27 default
  }
}

The other v27 changes (/ no longer escaped in values, a logger and post-processors per instance, the key instead of a sentence for an object hit, the dotted-language store calls and *Escaped options removed) have no switch; the debug warnings below show where they apply.

  • feat: with the default skipOnVariables: true, a missing interpolation variable is now logged in debug mode, once per string and variable: missed to pass in variable name for interpolating Hello {{name}}. The raw {{name}} reached the UI without any log line, even with debug: true, because the warning only ran with skipOnVariables: false. A variable passed as undefined and a missingInterpolationHandler still log nothing.
  • feat: i18next.hydrate(resources, lng) puts resources rendered on the server into the store and changes to the server's language, each only the first time. It does what react-i18next's useSSR did by writing resourceStore.data, options.ns, isInitialized, initializedStoreOnce and initializedLanguageOnce directly, and sets the same flags, so integrations can switch to it and stay compatible with code that still reads or writes them. On a clone it does nothing, as useSSR does: a clone shares its parent's store (one clone per request with i18next-http-middleware). Called before init(), it logs a warning and changes nothing.
  • feat: services.utils.reloadResources() lets a backend reload its bundles through i18next (as i18next.reloadResources(), with retries and the loaded event), instead of calling backendConnector.read() and loaded() itself as the reloadInterval of i18next-http-backend and i18next-chained-backend does. Without languages (no lng, no detector, the default fallbackLng), reloadResources() reloads nothing instead of throwing Cannot read properties of undefined (reading 'forEach'); a backend that also reloads preload passes its languages.
  • feat: backends and async language detectors can declare their calling convention with callbackApi (an instance or static property). true: read(language, namespace, callback), create(languages, namespace, key, fallbackValue, callback, options) and detect(callback); false: they return a promise or a value, and create gets the options as its fifth argument. Without it, i18next keeps guessing from the number of parameters (Function.length), which default and rest parameters change: i18next-chained-backend's create(..., clb = () => {}, opts = {}) has length 4 and never got its options (isUpdate), and i18next-http-backend's callback form of create has length 5, the length reserved for the callback-less form. Guessing is deprecated: in debug mode an unmarked backend or async detector logs a deprecation warning, once per init().
  • feat: isSafeLanguageCode(code) is exported for plugins that take a language from a request, a URL or storage: letters, digits, -, _, @ and . (no ..), at most 128 characters, not a prototype key. It is not a BCP 47 check, so en_US, zh_Hant_TW, sr@latin and de_DE.UTF-8 pass; markup, slashes and spaces do not. The language detector, i18next-http-middleware and i18next-http-backend each have their own rule today.
  • feat: use() logs a warning in debug mode when a second backend, language detector, i18nFormat or formatter replaces the first one; only one of each is used per instance, and losing an ICU setup this way was silent. As use() usually runs before init(), the warning is printed once init() has set up the logger.
  • feat(types): ParseKeysWithoutVariables<Ns, KPrefix>, the keys t() takes without options: their string has no variables, and a plural key is left out when its forms take count. A wrapper typed with it, like (key: ParseKeysWithoutVariables<'common'>) => t(key), compiles with strictInterpolationChecks without a cast.
  • feat(types): defaultVariables in CustomTypeOptions declares the variables interpolation.defaultVariables fills in at runtime (defaultVariables: { appName: string }). They become optional in the t() options, also with strictInterpolationChecks; passed, they keep their type.
  • feat(types): interpolationFormatSeparator in CustomTypeOptions for a custom interpolation.formatSeparator: the types split {{price, currency}} at a hard-coded ,, so with formatSeparator: ';' the format was not recognized. The per-call skipInterpolation option is typed, and returnedObjectHandler may return a value (what it returns is what t() returns; it was typed as returning void).
  • feat(types): SelectorFn, ApplyTarget, ConstrainTarget and GetSource are exported on purpose, under their current names. react-i18next imports them for Trans; they were importable only because every declaration in the type files counts as exported.
  • fix(types): with nsSeparator: false in CustomTypeOptions, the key union no longer contains nsfalsekey-style keys for the other namespaces, and a key that contains the text false (isfalsey) is no longer split at it, which typed its t() result as never.
  • fix: with clones (i18next-http-middleware makes one per request), saveMissing now checks that the namespace is loaded for the instance that misses the key. Each cloneInstance() pointed the parent's services.utils.hasLoadedNamespace at the new clone, and the backend connector, which all clones share, used that one: a key missing in one request was not saved (did not save key ... as the namespace ... was not yet loaded) while a newer request was still loading its language, and the parent's services.utils answered for the newest clone. A clone's services.utils is now bound to the clone, and the parent keeps its own. A direct services.backendConnector.saveMissing() call, like the missing keys route of i18next-http-middleware, still checks the newest clone (follow-up to #1413).
  • fix: dir() without a language (before init(), or with no language resolved) returns 'ltr' instead of 'rtl' ([discussion #2135](Why 'rtl' is default direction in case of language not found? i18next/i18next#2135)).
  • fix: t() before init() returns an empty string, as typed (with a warning when debug logging is already on); it returned undefined.
  • fix: off('a b', listener) removes the listener from both events, as on('a b', listener) adds it to both. It looked for an event named 'a b', so once('a b', listener) never removed its listener and ran it on every event.
  • deprecate: dotted languages in the resource store calls (getResource('en.translation.key'), addResource('en.translation.key', value), addResourceBundle('en.translation', resources)) log a deprecation warning in debug mode; they are removed in v27. Pass language, namespace and key as separate arguments.
  • deprecate: interpolation.prefixEscaped, suffixEscaped, nestingPrefixEscaped and nestingSuffixEscaped (inserted into the RegExp unescaped) log a deprecation warning in debug mode and are marked @deprecated; they are removed in v27. Pass the literal delimiters as prefix, suffix, nestingPrefix and nestingSuffix.
  • deprecate: compatibilityJSON is marked @deprecated (it has no effect since v24) and removed from the types in v27.
  • deprecate: a language code without a region that v27 canonicalizes differently logs a deprecation warning in debug mode: 'EN' stays 'EN' today and becomes 'en' in v27, 'iw' becomes 'he'. cleanCode: true already lower-cases them.
  • deprecate: when fallbackLng is not set, the first request for the default fallback language dev (loading it, or saving missing keys to it) logs a notice in debug mode: v27 defaults to fallbackLng: false and no longer requests dev. Set fallbackLng to your source language, or to 'dev' to keep the current behavior.

... (truncated)

Changelog

Sourced from i18next's changelog.

26.7.2

  • fix: the debug-mode deprecation warning for a language code without a region no longer says that v27 replaces aliases. 26.7.0 and 26.7.1 warned that v27 turns 'iw' into 'he' or 'tl' into 'fil' and asked you to rename them. v27 only gives such codes their canonical casing ('EN' becomes 'en', 'IW' becomes 'iw'), so iw, tl, eng and similar codes stay as they are. If you renamed them because of that warning, you can keep or restore the old codes. The warning now only appears when the casing changes.

26.7.1

  • fix: reloadResources() retries the bundles that failed to load. The load queue skipped them also when reloading, so a language whose first load failed (a backend or network outage at startup) stayed missing. i18next-http-backend 4.0.8, i18next-chained-backend 5.0.7 and i18next-locize-backend 10.0.5 reload through reloadResources() with i18next 26.7, so their reloadInterval no longer recovered from such a failure, as their own reload did before.
  • fix: reloadResources() without languages reloads the current languages and every language the backend loaded or tried to load, for the instance and its clones, as the API docs describe ("pass languages and namespaces if you don't want to reload all"). It reloaded only the current languages, so on a server (one clone per request with i18next-http-middleware) a backend's reloadInterval never refreshed the languages loaded for requests. It never requests cimode. With languages given, nothing changes.

26.7.0

The last 26.x minor before v27, which follows in about a week. It adds the APIs v27 builds on, and with debug: true it warns wherever a setup relies on something v27 changes. Most of the v27 defaults are existing options, so you can try them now:

i18next.init({
  debug: true, // prints the warnings below
  fallbackLng: 'en', // v27: fallbackLng defaults to false, set your source language (no implicit 'dev')
  returnEmptyString: false, // v27 default: an empty string falls back like a missing key
  cleanCode: true, // close to v27, which canonicalizes codes without a region ('EN' becomes 'en')
});
declare module 'i18next' {
  interface CustomTypeOptions {
    strictInterpolationChecks: true; // v27 default
    returnEmptyString: false; // v27 default
  }
}

The other v27 changes (/ no longer escaped in values, a logger and post-processors per instance, the key instead of a sentence for an object hit, the dotted-language store calls and *Escaped options removed) have no switch; the debug warnings below show where they apply.

  • feat: with the default skipOnVariables: true, a missing interpolation variable is now logged in debug mode, once per string and variable: missed to pass in variable name for interpolating Hello {{name}}. The raw {{name}} reached the UI without any log line, even with debug: true, because the warning only ran with skipOnVariables: false. A variable passed as undefined and a missingInterpolationHandler still log nothing.
  • feat: i18next.hydrate(resources, lng) puts resources rendered on the server into the store and changes to the server's language, each only the first time. It does what react-i18next's useSSR did by writing resourceStore.data, options.ns, isInitialized, initializedStoreOnce and initializedLanguageOnce directly, and sets the same flags, so integrations can switch to it and stay compatible with code that still reads or writes them. On a clone it does nothing, as useSSR does: a clone shares its parent's store (one clone per request with i18next-http-middleware). Called before init(), it logs a warning and changes nothing.
  • feat: services.utils.reloadResources() lets a backend reload its bundles through i18next (as i18next.reloadResources(), with retries and the loaded event), instead of calling backendConnector.read() and loaded() itself as the reloadInterval of i18next-http-backend and i18next-chained-backend does. Without languages (no lng, no detector, the default fallbackLng), reloadResources() reloads nothing instead of throwing Cannot read properties of undefined (reading 'forEach'); a backend that also reloads preload passes its languages.
  • feat: backends and async language detectors can declare their calling convention with callbackApi (an instance or static property). true: read(language, namespace, callback), create(languages, namespace, key, fallbackValue, callback, options) and detect(callback); false: they return a promise or a value, and create gets the options as its fifth argument. Without it, i18next keeps guessing from the number of parameters (Function.length), which default and rest parameters change: i18next-chained-backend's create(..., clb = () => {}, opts = {}) has length 4 and never got its options (isUpdate), and i18next-http-backend's callback form of create has length 5, the length reserved for the callback-less form. Guessing is deprecated: in debug mode an unmarked backend or async detector logs a deprecation warning, once per init().
  • feat: isSafeLanguageCode(code) is exported for plugins that take a language from a request, a URL or storage: letters, digits, -, _, @ and . (no ..), at most 128 characters, not a prototype key. It is not a BCP 47 check, so en_US, zh_Hant_TW, sr@latin and de_DE.UTF-8 pass; markup, slashes and spaces do not. The language detector, i18next-http-middleware and i18next-http-backend each have their own rule today.
  • feat: use() logs a warning in debug mode when a second backend, language detector, i18nFormat or formatter replaces the first one; only one of each is used per instance, and losing an ICU setup this way was silent. As use() usually runs before init(), the warning is printed once init() has set up the logger.
  • feat(types): ParseKeysWithoutVariables<Ns, KPrefix>, the keys t() takes without options: their string has no variables, and a plural key is left out when its forms take count. A wrapper typed with it, like (key: ParseKeysWithoutVariables<'common'>) => t(key), compiles with strictInterpolationChecks without a cast.
  • feat(types): defaultVariables in CustomTypeOptions declares the variables interpolation.defaultVariables fills in at runtime (defaultVariables: { appName: string }). They become optional in the t() options, also with strictInterpolationChecks; passed, they keep their type.
  • feat(types): interpolationFormatSeparator in CustomTypeOptions for a custom interpolation.formatSeparator: the types split {{price, currency}} at a hard-coded ,, so with formatSeparator: ';' the format was not recognized. The per-call skipInterpolation option is typed, and returnedObjectHandler may return a value (what it returns is what t() returns; it was typed as returning void).
  • feat(types): SelectorFn, ApplyTarget, ConstrainTarget and GetSource are exported on purpose, under their current names. react-i18next imports them for Trans; they were importable only because every declaration in the type files counts as exported.
  • fix(types): with nsSeparator: false in CustomTypeOptions, the key union no longer contains nsfalsekey-style keys for the other namespaces, and a key that contains the text false (isfalsey) is no longer split at it, which typed its t() result as never.
  • fix: with clones (i18next-http-middleware makes one per request), saveMissing now checks that the namespace is loaded for the instance that misses the key. Each cloneInstance() pointed the parent's services.utils.hasLoadedNamespace at the new clone, and the backend connector, which all clones share, used that one: a key missing in one request was not save...

    Description has been truncated

…pdates

Bumps the dev-minor group with 9 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.6.5` | `26.6.6` |
| [antd](https://github.com/ant-design/ant-design) | `6.6.6` | `6.7.0` |
| [eslint](https://github.com/eslint/eslint) | `10.13.0` | `10.14.0` |
| [globals](https://github.com/sindresorhus/globals) | `17.13.0` | `17.14.0` |
| [i18next](https://github.com/i18next/i18next) | `26.5.2` | `26.7.2` |
| [react-i18next](https://github.com/i18next/react-i18next) | `17.1.0` | `17.1.13` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.71.2` | `8.72.1` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.5` | `5.1.0` |
| [zustand](https://github.com/pmndrs/zustand) | `5.0.15` | `5.1.0` |



Updates `@types/node` from 26.6.5 to 26.6.6
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `antd` from 6.6.6 to 6.7.0
- [Release notes](https://github.com/ant-design/ant-design/releases)
- [Changelog](https://github.com/ant-design/ant-design/blob/master/CHANGELOG.en-US.md)
- [Commits](ant-design/ant-design@6.6.6...6.7.0)

Updates `eslint` from 10.13.0 to 10.14.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.13.0...v10.14.0)

Updates `globals` from 17.13.0 to 17.14.0
- [Release notes](https://github.com/sindresorhus/globals/releases)
- [Commits](sindresorhus/globals@v17.13.0...v17.14.0)

Updates `i18next` from 26.5.2 to 26.7.2
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.5.2...v26.7.2)

Updates `react-i18next` from 17.1.0 to 17.1.13
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v17.1.0...v17.1.13)

Updates `typescript-eslint` from 8.71.2 to 8.72.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.1/packages/typescript-eslint)

Updates `vitest` from 5.0.5 to 5.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.1.0/packages/vitest)

Updates `zustand` from 5.0.15 to 5.1.0
- [Release notes](https://github.com/pmndrs/zustand/releases)
- [Commits](pmndrs/zustand@v5.0.15...v5.1.0)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.6.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor
- dependency-name: antd
  dependency-version: 6.7.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: eslint
  dependency-version: 10.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: globals
  dependency-version: 17.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: i18next
  dependency-version: 26.7.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: react-i18next
  dependency-version: 17.1.13
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-minor
- dependency-name: typescript-eslint
  dependency-version: 8.72.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: vitest
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
- dependency-name: zustand
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 10, 2026
@xinghe-labs
xinghe-labs merged commit 926849d into main Nov 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant