[dependabot]

Bumps the dev-dependencies group with 5 updates:

Package	From	To
chokidar	5.0.0	6.0.0
i18next	26.5.10	26.5.11
i18next-browser-languagedetector	8.2.2	8.2.3
react-hook-form	7.90.0	7.91.0
react-i18next	17.1.8	17.1.9

Updates chokidar from 5.0.0 to 6.0.0

Release notes

Sourced from chokidar's releases.

6.0.0

High-level changes

• Rewrote the watcher around a single observation pipeline. Backend callbacks are treated as invalidations and confirmed with lstat, stat, or readdir before any event is emitted, so the final state after a burst of changes matches the filesystem.
• Added native recursive watching through fs.watch({ recursive: true }). The default auto backend uses it on macOS and Windows and per-directory watching elsewhere.
• Shared native handles across watchers and opened them per directory only: files no longer own handles. This fixes EBADF errors when watching many files on macOS (#1385, #1452).
• Replaced fs.watchFile with Chokidar-owned stat polling. Poll loops are shared across watchers at the fastest requested interval.
• Required Node.js 22.22 or later.

API changes

• Added the backend option: 'auto' (default), 'native', 'native-recursive', or 'polling'.
  • usePolling: true remains as a deprecated alias for backend: 'polling'.
• Renamed interval and binaryInterval to pollingInterval and pollingBinaryInterval.
  • The old names remain as deprecated aliases; the new names win when both are given.
• Changed the atomic default to false with polling. An explicit value is preserved.
• Made close() terminal: add() now throws once closing has started. Construct a new watcher instead.
• Validated options in the constructor: invalid backend, atomic, depth, awaitWriteFinish, and polling intervals throw TypeError.
• Emitted errors from add() as error events instead of unhandled rejections (#1378).
• Made getWatched() return a null-prototype object, so a watched directory named __proto__ is listed (#1493). Use Object.hasOwn() instead of hasOwnProperty() on the result.
• Stopped applying ignored to directories above a path passed to watch() or add(), so a missing path is still watched through its parent (#1374). Other entries in those directories are still filtered.

Fixes

• Fixed a 100% CPU loop when the process working directory containing a relatively watched file was deleted (#1474).
• Fixed watching a filesystem root, which emitted unlink and unlinkDir for every entry (#1184, #452).
• Fixed UNKNOWN errors from fs.watch on macOS sockets, which prevented watching /var/run (#1391).
• Fixed a symlink whose target passes through a regular file (ENOTDIR) disabling watching of its directory and preventing ready (#1476).
• Fixed files created in a newly added directory between its scan and watch registration being missed (#1471).
• Fixed watching a missing nested path stopping its parent directory's subtree from being watched (#1470).
• Fixed false change events on Windows when many sibling files are written (#1466).
• Fixed duplicate add events for unchanged files under directory activity (#1465).
• Fixed replacing a watched directory with a file of the same name hanging the process (#1464).
• Fixed persistent watching stopping after a watched directory was removed (#1463).
• Fixed a deleted watched path not being reported when recreated: previously only a deleted file that was the sole watched path was watched for its return. Any path passed to watch() or add() is now awaited from its nearest existing parent.
• Fixed event throttling discarding updates; the newest differing change is now replayed when the window closes (#1455).
• Fixed relative ignored paths; relative strings now resolve against cwd or the process working directory (#1436).
• Fixed files not being detected when their directory did not exist before watching (#1422).
• Fixed removed files being reported as unlinkDir instead of unlink (#1421).
• Fixed ignored files and directories still being watched in WSL (#1418).
• Fixed change being reported for every file when one file changed under Deno (#1417).
• Fixed changes not being detected after the second save (#1399).
• Fixed renaming a watched directory that contains subdirectories on Windows (#1380, #1398).
• Fixed re-watching a path not honoring ignoreInitial (#1386).
• Fixed EISDIR errors during the initial scan of network drives (#1376).
• Fixed watching an array of absolute file paths (#1366).
• Fixed unwatching a deleted watched directory on Windows, contributed by @​sapphi-red in [pull request #1467](paulmillr/chokidar#1467).
• Documented that unwatched paths stay ignored until they are added again (#1439).

Misc

... (truncated)

Changelog

Sourced from chokidar's changelog.

6.0.0 (2026-10-19)

High-level changes

• Rewrote the watcher around a single observation pipeline. Backend callbacks are treated as invalidations and confirmed with lstat, stat, or readdir before any event is emitted, so the final state after a burst of changes matches the filesystem.
• Added native recursive watching through fs.watch({ recursive: true }). The default auto backend uses it on macOS and Windows and per-directory watching elsewhere.
• Shared native handles across watchers and opened them per directory only: files no longer own handles. This fixes EBADF errors when watching many files on macOS (#1385, #1452).
• Replaced fs.watchFile with Chokidar-owned stat polling. Poll loops are shared across watchers at the fastest requested interval.
• Required Node.js 22.22 or later.

API changes

• Added the backend option: 'auto' (default), 'native', 'native-recursive', or 'polling'.
  • usePolling: true remains as a deprecated alias for backend: 'polling'.
• Renamed interval and binaryInterval to pollingInterval and pollingBinaryInterval.
  • The old names remain as deprecated aliases; the new names win when both are given.
• Changed the atomic default to false with polling. An explicit value is preserved.
• Made close() terminal: add() now throws once closing has started. Construct a new watcher instead.
• Validated options in the constructor: invalid backend, atomic, depth, awaitWriteFinish, and polling intervals throw TypeError.
• Emitted errors from add() as error events instead of unhandled rejections (#1378).
• Made getWatched() return a null-prototype object, so a watched directory named __proto__ is listed (#1493). Use Object.hasOwn() instead of hasOwnProperty() on the result.
• Stopped applying ignored to directories above a path passed to watch() or add(), so a missing path is still watched through its parent (#1374). Other entries in those directories are still filtered.

Fixes

• Fixed a 100% CPU loop when the process working directory containing a relatively watched file was deleted (#1474).
• Fixed watching a filesystem root, which emitted unlink and unlinkDir for every entry (#1184, #452).
• Fixed UNKNOWN errors from fs.watch on macOS sockets, which prevented watching /var/run (#1391).
• Fixed a symlink whose target passes through a regular file (ENOTDIR) disabling watching of its directory and preventing ready (#1476).
• Fixed files created in a newly added directory between its scan and watch registration being missed (#1471).
• Fixed watching a missing nested path stopping its parent directory's subtree from being watched (#1470).
• Fixed false change events on Windows when many sibling files are written (#1466).
• Fixed duplicate add events for unchanged files under directory activity (#1465).
• Fixed replacing a watched directory with a file of the same name hanging the process (#1464).
• Fixed persistent watching stopping after a watched directory was removed (#1463).
• Fixed a deleted watched path not being reported when recreated: previously only a deleted file that was the sole watched path was watched for its return. Any path passed to watch() or add() is now awaited from its nearest existing parent.
• Fixed event throttling discarding updates; the newest differing change is now replayed when the window closes (#1455).
• Fixed relative ignored paths; relative strings now resolve against cwd or the process working directory (#1436).
• Fixed files not being detected when their directory did not exist before watching (#1422).
• Fixed removed files being reported as unlinkDir instead of unlink (#1421).
• Fixed ignored files and directories still being watched in WSL (#1418).
• Fixed change being reported for every file when one file changed under Deno (#1417).
• Fixed changes not being detected after the second save (#1399).
• Fixed renaming a watched directory that contains subdirectories on Windows (#1380, #1398).
• Fixed re-watching a path not honoring ignoreInitial (#1386).
• Fixed EISDIR errors during the initial scan of network drives (#1376).
• Fixed watching an array of absolute file paths (#1366).
• Fixed unwatching a deleted watched directory on Windows, contributed by @​sapphi-red in [pull request #1467](paulmillr/chokidar#1467).
• Documented that unwatched paths stay ignored until they are added again (#1439).

... (truncated)

Commits

• 4130839 Release 6.0.0.
• 53f3256 Bump devdeps
• 11ad48f More fixes
• b6812dd Change date
• 706ef2c Merge pull request #1492 from paulmillr/jg/private-public
• d85f4cc chore: expose tested members
• 97e1b93 Add changelog
• 8d5c07d More v6 fixes
• 7af52df Bump ci release.yml
• a0b05d9 Merge pull request #1478 from paulmillr/jg/sponsors
• Additional commits viewable in compare view

Updates i18next from 26.5.10 to 26.5.11

Release notes

Sourced from i18next's releases.

v26.5.11

• fix: a nested false, 0 or '' is now returned when a flat key with the same dotted name also exists. With { a: { b: false }, 'a.b': 'flat' }, getResource('en', 'translation', 'a.b') and t('a.b') returned 'flat': the nested result was checked for truthiness, so these present values fell through to the flat-key lookup. Without such a flat key they were already returned. A nested null, which is not a valid lookup by default (returnNull: false), still falls back to the flat key. Thanks @​lprnmns (#2461).

Changelog

Sourced from i18next's changelog.

26.5.11

• fix: a nested false, 0 or '' is now returned when a flat key with the same dotted name also exists. With { a: { b: false }, 'a.b': 'flat' }, getResource('en', 'translation', 'a.b') and t('a.b') returned 'flat': the nested result was checked for truthiness, so these present values fell through to the flat-key lookup. Without such a flat key they were already returned. A nested null, which is not a valid lookup by default (returnNull: false), still falls back to the flat key. Thanks @​lprnmns (#2461).

Commits

• a0ab5e9 26.5.11
• a08cf9e build
• 81677f9 changelog for 26.5.11
• a92934e fix: keep a nested null falling back to a flat key
• ad6e1ac fix: preserve falsy nested resource values (#2461)
• See full diff in compare view

Updates i18next-browser-languagedetector from 8.2.2 to 8.2.3

Changelog

Sourced from i18next-browser-languagedetector's changelog.

8.2.3

• fix: the subdomain detector now detects language tags with script and region subtags, so pt-BR.site.com, zh-Hans-CN.site.com, es-419.site.com and sr-Latn.site.com are detected as pt-BR, zh-Hans-CN, es-419 and sr-Latn. The pattern only accepted 2 to 5 word characters, without hyphens. Other subdomains like staging or preview deployment labels (myapp-git-branch-team.vercel.app) are still not taken for a language, and everything detected before is still detected. Thanks @​lprnmns 328

Commits

• fa81be3 8.2.3
• dbe4ee2 release
• 4435b3d fix: only take language-tag shaped subdomains for a language
• ceef464 fix: detect hyphenated locales in subdomains (#328)
• See full diff in compare view

Updates react-hook-form from 7.90.0 to 7.91.0

Release notes

Sourced from react-hook-form's releases.

Version 7.91.0

🐞 Fixes

• Fix useFieldArray not updating rows when using setValue or setValues (#13842, #13939)
• Fix useFieldArray not unregistering values correctly on unmount (#13843)
• Fix field registration without a value incorrectly adding array rows (#13846, #13849)
• Fix useFieldArray reindexing fields incorrectly when array rules are registered (#13873)
• Fix useFieldArray losing validation rules after reset() (#13940)
• Fix stale field array validation results after array changes (#13888)
• Fix useFieldArray validation after submission in onBlur mode (#13867)
• Fix dirty state updates when setValues changes field arrays (#13870)
• Fix stale asynchronous validation results after reset() and unregister() (#13908, #13912, #13934)
• Fix Controller validation using stale DOM values (#13880)
• Fix isValid not updating correctly after reset() and subsequent changes (#13847, #13930)
• Fix handleSubmit leaving isSubmitting active when validation throws (#13905)
• Fix empty validation message arrays being treated as errors (#13937)
• Fix delayed validation errors not being flushed on blur (#13861)
• Fix form state subscriptions and validity updates (#13866, #13877, #13906)
• Fix dirty state tracking and resetField() with falsy values (#13868, #13900)
• Fix unregister retaining validation rules when using keepValue (#13891)
• Fix <Form /> handling of JSON, URL-encoded, multipart and plain-text submissions (#13848, #13854, #13874, #13893, #13907, #13915, #13926)
• Fix useWatch not updating default values when the watched name changes (#13859)
• Fix select options being lost before the form is ready (#13872)
• Fix useForm retaining removed options and disabled state (#13882, #13883, #13889, #13898)
• Fix progressive required attributes (#13924)
• Fix numeric zero maxLength validation (#13851)
• Fix object comparison for null-prototype objects and sparse arrays (#13853, #13855, #13857)
• Fix cloneObject handling objects with a constructor key (#13875)
• Fix setValue handling null-prototype objects (#13916)
• Fix form-level validation error types (#13860)
• Fix useForm mutating the externally provided errors object (#13896)
• Fix stale NaN and invalid date validation results (#13910)

⚡ Performance Improvements

• Avoid unnecessary copies when calling getValues() (#13894)
• Reduce unnecessary <Form /> re-renders (#13899)

🧹 Refactors

• Simplify multipart Content-Type handling (#13926)
• Improve internal types and remove unnecessary type assertions (#13871, #13886)
• Clean up memoized component display names (#13897)
• Fix JSDoc examples (#13895)

🧪 Tests

• Add coverage for disabled field array operations (#13841)
• Expand regression coverage for useFieldArray, reset, validation and form state

... (truncated)

Changelog

Sourced from react-hook-form's changelog.

[7.91.0] - 2026-10-24

Changed

• Improve performance of Form by reading control from context to avoid unnecessary re-renders
• Improve performance of getValues by avoiding unnecessary shallow copies
• Simplify multipart content-type header filtering
• Align form-level validation error types

Fixed

• useFieldArray not registering array rules again after reset
• setValue not updating field array rows when a parent object is set
• createFormControl keeping a newer change's error when an older isValid pass settles
• validate treating an empty message array as valid
• reset releasing keepIsValid on the next field change or field array operation
• register only emitting the progressive required attribute when the rule is on
• createFormControl dropping the async result of a field unregistered while it validates
• createFormControl supporting null-prototype objects in setValue
• Form handling case-insensitive and parameterized multipart encType
• createFormControl ignoring a stale NaN or Invalid Date validation result
• Settle submit state when validation throws
• Form letting fetch set the multipart boundary for a multipart content-type header
• createFormControl ignoring a stale built-in validity result after reset
• useForm running the initial validity check when a child subscribed first
• Form sending a text/plain body for a text/plain content type
• createFormControl copying the errors prop instead of writing into it
• useForm resetting resetOptions when removed from props
• createFormControl handling falsy values correctly in _getDirty and resetField
• unregister dropping the field's rules when keepValue keeps only its value
• useForm clearing errors when the errors option is removed or set to undefined
• useFieldArray dropping a validation result once the array has changed
• reset keeping retained fields disabled
• useForm re-enabling the form when the disabled option is removed
• formState producing a new validatingFields reference when it changes
• validateField validating the stored value of Controller fields with a DOM ref
• useForm resetting progressive option when removed from props
• cloneObject copying plain objects that have a constructor key
• useFieldArray reindexing row fields when the array has rules
• Form matching JSON content types case-insensitively
• deepEqual comparing keys as own properties instead of via in
• register keeping select options picked before the form is ready
• Report isReady to useFormState mounted with the form
• useFieldArray revalidating array operations after submit in onBlur mode
• getDirtyFields handling null or undefined form values when clearing a field
• setValue updating isDirty when shouldDirty fills a field array
• delayError flushing the delayed error on blur when blur also validates
• useWatch using the new defaultValue when the watched name changes
• deepEqual comparing sparse array lengths
• Form sending a url-encoded body for a url-encoded content type

... (truncated)

Commits

• de3c946 7.91.0
• da618cb Revert "🐞 fix(reset): keep mounted Controllers registered so submit still val...
• e715d44 🧴 fix remove optional chain
• eed8086 🐞 fix(useFieldArray): register the array rules again after reset (#13940)
• fe960d4 🐞 fix(setValue): update field array rows when the parent object is set (#13939)
• 0f3e977 🐞 fix(createFormControl): keep a newer change's error when an older isValid p...
• 33f65e5 🐞 fix(getValidateError): treat an empty message array from validate as valid ...
• a72bcd7 Revert "🐞 fix(objectHasFunction): check own properties to ignore Object.proto...
• dee9424 🐞 fix(reset): release keepIsValid on the next field change or field array op ...
• 76c0b3d 🐞 fix(reset): keep mounted Controllers registered so submit still validates t...
• Additional commits viewable in compare view

Updates react-i18next from 17.1.8 to 17.1.9

Changelog

Sourced from react-i18next's changelog.

17.1.9

• fix(useTranslation): namespaces added to or removed from the ns array are now picked up. The hook used the array itself as the useMemo dependency list, and React only compares the entries both lists have in common when its length changes, so going from useTranslation(['nsA']) to useTranslation(['nsA', 'nsB']) kept returning ['nsA']: React warned that the dependency array changed size, nsB was never loaded, and with nsMode: 'fallback' keys only in nsB rendered as the key. Removing a namespace kept the old list the same way. The namespaces are now compared by content, so a growing list loads the new namespace (suspending until it is loaded, as switching from 'nsA' to 'nsB' already does) and t uses it. Lists that keep their length behave as before. Thanks @​lprnmns (#1945).

Commits

• 4f4236d 17.1.9
• e1a6945 build
• 8e9b59e changelog for 17.1.9
• 46564b6 fix: refresh translations when namespaces are added (#1945)
• See full diff in compare view

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 commands and options

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions