remix - npm Package Versions

v2.13.0

Date: 2024-10-11

What's Changed

Stabilized APIs

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)~~
  • ⚠️ This flag was not intended to stabilize in Remix v2 and was reverted back to future.unstable_optimizeDeps in 2.13.1
• future.unstable_lazyRouteDiscovery → future.v3_lazyRouteDiscovery (Docs)
• future.unstable_singleFetch → future.v3_singleFetch (Docs)

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, #10092)
  • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery
  • future.unstable_optimizeDeps -> future.v3_optimizeDeps
  • future.unstable_singleFetch -> future.v3_singleFetch

Patch Changes

• @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)
  • 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
• @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)

Updated Dependencies

• react-router-dom@6.27.0
• @remix-run/router@1.20.0

Changes by Package

• 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

v2.12.1

Date: 2024-09-19

Patch Changes

• @remix-run/dev - Properly abort request.signal during vite dev when the node response is closed (#9976)
• @remix-run/dev - CSS imports with ?inline, ?inline-css and ?raw are no longer incorrectly injected during SSR in development (#9910)
• @remix-run/server-runtime: Single Fetch: Fix types when loader, action, clientLoader, or clientAction return a mixture of bare objects, json(...), defer(...), and unstable_data(...). (#9999)
• @remix-run/node/@remix-run/cloudflare/@remix-run/deno - Single Fetch: Re-export interface Future through runtime packages so that pnpm doesn't complain about @remix-run/server-runtime not being a dependency (#9982)
  • If you've already opted into Single Fetch, you can change your Single Fetch type augmentation in vite.config.ts to augment @remix-run/node (or cloudflare/deno) instead of @remix-run/server-runtime

Changes by Package

• @remix-run/cloudflare
• @remix-run/deno
• @remix-run/dev
• @remix-run/node
• @remix-run/server-runtime

Full Changelog: v2.12.0...v2.12.1