Update remix monorepo to v2.13.0

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

v2.13.0

Compare Source

Minor Changes

• Stabilize the future.unstable_optimizeDeps flag into future.v3_optimizeDeps (#​10092)
• Stabilize React Router APIs in Remix (#​9980)
  • Adopt stabilized React Router APIs internally
    • Single Fetch: unstable_dataStrategy -> dataStrategy
    • Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
  • Stabilize public-facing APIs
    • Single Fetch: unstable_data() -> data()
    • unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
    • unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
• Stabilize future flags (#​10072)
  • future.unstable_singleFetch -> future.v3_singleFetch
  • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

• Stop passing request.signal as the renderToReadableStream signal to abort server rendering for cloudflare/deno runtimes because by the time that request is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#​10047)

  • This has been incorrect for some time, but only recently exposed due to a bug in how we were aborting requests when running via remix vite:dev because we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closed ReadableStream.
  • This has likely not shown up in any production scenarios because cloudflare/deno production runtimes are (correctly) not aborting the request.signal on successful renders
  • The built-in entry.server files no longer pass a signal to renderToReadableStream because adding a timeout-based abort signal to the default behavior would constitute a breaking change
  • Users can configure this abort behavior via their own entry.server via remix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix apps

• Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#​10046)

• Updated dependencies:

  • @remix-run/[email protected]
  • @remix-run/[email protected]

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

v2.13.0

Compare Source

Minor Changes

• Stabilize React Router APIs in Remix (#​9980)
  • Adopt stabilized React Router APIs internally
    • Single Fetch: unstable_dataStrategy -> dataStrategy
    • Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
  • Stabilize public-facing APIs
    • Single Fetch: unstable_data() -> data()
    • unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
    • unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
• Stabilize future flags (#​10072)
  • future.unstable_singleFetch -> future.v3_singleFetch
  • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery

Patch Changes

• Fix bug with clientLoader.hydrate in a layout route when hydrating with bubbled errors (#​10063)
• Updated dependencies:
  • @remix-run/[email protected]

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

v2.13.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.