@remix-run/server-runtime
Advanced tools
Changelog
v2.13.1
Date: 2024-10-11
@remix-run/dev
- Revert future.v3_optimizeDeps
back to future.unstable_optimizeDeps
as it was not intended to stabilize in Remix v2 (#10099)Full Changelog: v2.13.0...v2.13.1
Changelog
v2.13.0
Date: 2024-10-11
This release stabilizes a handful of "unstable" APIs in preparation for the pending React Router v7 release (see these posts for more info):
unstable_data
→ data
(for use with Single Fetch)unstable_flushSync
→ flushSync
(useSubmit
, fetcher.load
, fetcher.submit
)unstable_viewTransition
→ viewTransition
(<Link>
, <Form>
, useNavigate
, useSubmit
)future.unstable_optimizeDeps
→ future.v3_optimizeDeps
(Docs)~~
future.unstable_optimizeDeps
in 2.13.1
future.unstable_lazyRouteDiscovery
→ future.v3_lazyRouteDiscovery
(Docs)future.unstable_singleFetch
→ future.v3_singleFetch
(Docs)unstable_dataStrategy
-> dataStrategy
unstable_patchRoutesOnNavigation
-> patchRoutesOnNavigation
unstable_data()
-> data()
unstable_viewTransition
-> viewTransition
(Link
, Form
, navigate
, submit
)unstable_flushSync>
-> <Link viewTransition>
(Link
, Form
, navigate
, submit
, useFetcher
)future.unstable_lazyRouteDiscovery
-> future.v3_lazyRouteDiscovery
future.unstable_optimizeDeps
-> future.v3_optimizeDeps
future.unstable_singleFetch
-> future.v3_singleFetch
@remix-run/dev
- 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)
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
request.signal
on successful rendersentry.server
files no longer pass a signal
to renderToReadableStream
because adding a timeout-based abort signal to the default behavior would constitute a breaking changeentry.server
via remix reveal entry.server
, and the template entry.server files have been updated with an example approach for newly created Remix apps@remix-run/express
- Fix adapter logic for aborting request.signal
so we don't incorrectly abort on the close
event for successful requests (#10046)@remix-run/react
- Fix bug with clientLoader.hydrate
in a layout route when hydrating with bubbled errors (#10063)create-remix
@remix-run/architect
@remix-run/cloudflare
@remix-run/cloudflare-pages
@remix-run/cloudflare-workers
@remix-run/css-bundle
@remix-run/deno
@remix-run/dev
@remix-run/eslint-config
@remix-run/express
@remix-run/node
@remix-run/react
@remix-run/serve
@remix-run/server-runtime
@remix-run/testing
Full Changelog: v2.12.1...v2.13.0