Update remix monorepo to v2.12.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/dev (source)	2.11.2 -> 2.12.0
@remix-run/react (source)	2.11.2 -> 2.12.0
@remix-run/serve (source)	2.11.2 -> 2.12.0

---

Release Notes

remix-run/remix (@​remix-run/dev)

v2.12.0

Compare Source

Minor Changes

• New future.unstable_optimizeDeps flag for automatic dependency optimization (#​9921)
  • You can now opt-in to automatic dependency optimization during development by using the future.unstable_optimizeDeps future flag
  • For details, check out the docs at Guides > Dependency optimization
  • For users who were previously working around this limitation, you no longer need to explicitly add routes to Vite's optimizeDeps.entries nor do you need to disable the remix-dot-server plugin

Patch Changes

• Handle circular dependencies in modulepreload manifest generation (#​9917)
• Fix dest already exists build errors by only moving SSR assets to the client build directory when they're not already present on disk (#​9901)
• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

remix-run/remix (@​remix-run/react)

v2.12.0

Compare Source

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 #​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: #​1757
  • This specific hydration issue would then cause this React v17 only looping issue: #​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
    }
  }
  
  export default defineConfig({
    plugins: [
      remix({
        future: {
          unstable_singleFetch: true, // 👈 enable single-fetch
        },
      }),
    ],
  });

  For more information, see Guides > Single Fetch in our docs.

• Clarify wording in default HydrateFallback console warning (#​9899)

• Updated dependencies:

  • @remix-run/[email protected]

remix-run/remix (@​remix-run/serve)

v2.12.0

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]
  • @remix-run/[email protected]

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.