chore(deps): bump the production group across 1 directory with 3 updates

[dependabot]

Bumps the production group with 3 updates in the /web directory: i18next, react-hook-form and react-i18next.

Updates i18next from 26.4.0 to 26.4.2

Release notes

Sourced from i18next's releases.

v26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

v26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

Changelog

Sourced from i18next's changelog.

26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

Commits

• 4dba50f 26.4.2
• e436b62 build
• d955fb0 fix: stringify formatter results in nested values, changelog v26.4.2
• dfafa3c fix: keep replacement patterns literal in nested values (#2447)
• 3c9981e chore: keep dev-only and local files out of the npm package
• c057ee0 26.4.1
• 02e3e16 changelog v26.4.1
• 6f198f2 fix(types): allow selector keyPrefix in getFixedT under enableSelector 'stric...
• See full diff in compare view

Updates react-hook-form from 7.86.0 to 7.87.0

Release notes

Sourced from react-hook-form's releases.

Version 7.87.0

✨ Features

• Add shouldTouch option to trigger() ([#13671](react-hook-form/react-hook-form#13671))

  setValue already supported shouldTouch; trigger() now does too. This allows you to mark field(s) as touched after manual or programmatic validation, such as validate-on-mount or multi-step form navigation, without needing a setValue workaround:

  // Mark a single field as touched after validating it
  await trigger('firstName', { shouldTouch: true });
  // Mark every mounted field as touched after validating the whole form
  await trigger(undefined, { shouldTouch: true });

• Add OpaqueTypes registry for opaque leaf types ([#13676](react-hook-form/react-hook-form#13676))

  Recursive type helpers (Path, DeepPartial, DeepRequired, FieldErrorsImpl, etc.) previously stopped only at Primitive | BrowserNativeObject. As a result, rich third-party value types such as Dayjs and Decimal could be recursively traversed member-by-member, potentially causing TypeScript to report "Excessive complexity" diagnostics on large form types.

  You can now register a type as an opaque leaf via declaration merging:

  import type { Dayjs } from 'dayjs';
  declare module 'react-hook-form' {
  interface OpaqueTypes {
  dayjs: Dayjs;
  }
  }

  While the registry is empty, types remain identical to the existing behavior. This is purely opt-in.

🐞 Fixes

• Fix inconsistent behavior among useController().field.onChange()-like APIs. ([#13673](react-hook-form/react-hook-form#13673))
• Fix Controller under a null parent submitting undefined instead of a value. ([#13675](react-hook-form/react-hook-form#13675))
• Fix ERR_MODULE_NOT_FOUND when resolving react-hook-form due to a react-server declaration in Next.js builds. ([#13682](react-hook-form/react-hook-form#13682))
• Fix useWatch never reconciling when an Activity subtree is hidden on its first render. ([#13683](react-hook-form/react-hook-form#13683))
• Fix resetField not recomputing isValid for subscribe-only consumers. ([#13684](react-hook-form/react-hook-form#13684))
• Fix generateWatchOutput ignoring defaultValue for an array of names. ([#13686](react-hook-form/react-hook-form#13686))
• Fix useFormState never reconciling when an Activity subtree is hidden on its first render. ([#13687](react-hook-form/react-hook-form#13687))

❤️ Thank You

Thanks to @​giaBaoJS, @​dfedoryshchev, @​Alioth-91, @​Masatoshi0227, @​modosc, and @​bluebill1049 for their contributions! 🎉

Changelog

Sourced from react-hook-form's changelog.

[7.87.0] - 2026-08-30

Added

• shouldTouch option for trigger()
• OpaqueTypes registry for opaque leaf types

Fixed

• Inconsistent behavior among useController().field.onChange()-like APIs
• Controller under a null parent submitting undefined instead of a value
• ERR_MODULE_NOT_FOUND resolving react-hook-form due to a react-server declaration (Next.js builds)
• useWatch never reconciling when an Activity subtree is hidden on its first render
• resetField not recomputing isValid for subscribe-only consumers
• generateWatchOutput ignoring defaultValue for an array of names
• useFormState never reconciling when an Activity subtree is hidden on its first render

Commits

• 29af888 7.87.0
• 1eeab63 🐞 fix(useFormState): never reconciles when an Activity subtree is hidden on i...
• 145441c 🐞 fix(generateWatchOutput): defaultValue is ignored for an array of names (#1...
• 1fb065c 🐞 fix(resetField): isValid not recomputed for subscribe-only consumers (#13684)
• 2f7380e 🧹refactor: use continue instead of return in setFieldValues' hasOwnProper...
• 1b0a314 📖 remove comment
• a457ca7 🐞 fix #13680: useWatch never reconciles when an Activity subtree is hidden on...
• bb3360f 🐞 fix #13681 issue: ERR_MODULE_NOT_FOUND, Can't resolve react-hook-form due t...
• f646948 🪅 feat: add OpaqueTypes registry for opaque leaf types (#13676)
• e17a95c 🧇 chore: scope the lock workflow to issues so its scheduled run can finish (#...
• Additional commits viewable in compare view

Updates react-i18next from 17.0.12 to 17.0.13

Changelog

Sourced from react-i18next's changelog.

17.0.13

• fix(types): the selector-form keyPrefix overload of useTranslation() is now available under enableSelector: 'strict'. useTranslation was gated on true | 'optimize' only, so under 'strict' it resolved to the legacy signature and the selector overload disappeared entirely (keyPrefix: ($) => $.ns.foo failed with Type '($: any) => any' is not assignable to type 'undefined'). Trans already handled all three modes. Companion to the same fix for getFixedT in i18next#2446. Thanks @​hovelopin (#1930).

Commits

• addf646 17.0.13
• 7c634ee changelog v17.0.13
• 5ceefb0 fix(types): allow selector keyPrefix in useTranslation under enableSelector '...
• aa7ba52 chore(examples): require activesupport >= 7.2.3.1 in the RN Gemfiles
• ec0bb4e chore(examples): drop react_native_windows and the RN Gemfile.locks
• aa5fc43 build
• See full diff in compare view

[dependabot]

Labels

The following labels could not be found: dependencies, frontend. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.