build(deps): bump @remix-run/react from 2.10.2 to 2.12.1

[dependabot]

Bumps @remix-run/react from 2.10.2 to 2.12.1.

Release notes

Sourced from @​remix-run/react's releases.

v2.12.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2121

v2.12.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2120

v2.11.2

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2112

v2.11.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2111

v2.11.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v21110

v2.10.3

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2103

Changelog

Sourced from @​remix-run/react's changelog.

2.12.1

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.12.1

2.12.0

Patch Changes

• Lazy Route Discovery: Sort /__manifest query parameters for better caching (#9888)

• Single Fetch: fix revalidation behavior bugs (#9938)

  • With Single Fetch, existing routes revalidate by default
  • This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
  • There are two conditions that will trigger granular revalidation:
    • If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
    • If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
  • When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
    • For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a

• Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)

  • Reverts the logic originally added in Remix v1.18.0 via remix-run/remix#6409
  • This was added to resolve an issue that could arise when doing quick back/forward history navigations while JS was loading which would cause a mismatch between the server matches and client matches: remix-run/remix#1757
  • This specific hydration issue would then cause this React v17 only looping issue: remix-run/remix#1678
  • The URL comparison that we added in 1.18.0 turned out to be subject to false positives of it's own which could also put the user in looping scenarios
  • Remix v2 upgraded it's minimal React version to v18 which eliminated the v17 hydration error loop
  • React v18 handles this hydration error like any other error and does not result in a loop
  • So we can remove our check and thus avoid the false-positive scenarios in which it may also trigger a loop

• Single Fetch: Improved typesafety (#9893)

  If you were already using previously released unstable single-fetch types:

  • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
  • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
  • Replace UIMatch_SingleFetch type helper with UIMatch
  • Replace MetaArgs_SingleFetch type helper with MetaArgs

  Then you are ready for the new typesafety setup:

  // vite.config.ts
  declare module "@​remix-run/server-runtime" {
  interface Future {
  unstable_singleFetch: true; // 👈 enable types for single-fetch

... (truncated)

Commits

• e596b9b chore: Update version for release (#10007)
• b72cc1a chore: Update version for release (pre) (#10000)
• e947032 chore: Update version for release (#9965)
• e55a213 chore: Update version for release (pre) (#9964)
• 5ee7af7 Bump router (#9963)
• b629eae chore: Update version for release (pre) (#9959)
• f4b4420 Align single fetch prefetching with new revalidation logic (#9958)
• 61e83ec chore: Update version for release (pre) (#9953)
• 5900332 Fix HDR for single fetch (#9954)
• 1eed6bf chore: Update version for release (pre) (#9946)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Superseded by #181.