chore: Update version for release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

@remix-run/dev@2.9.0

Minor Changes

• New future.unstable_singleFetch flag (#8773)

  • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
  • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
    • If you need to return a custom status code or custom response headers, you can still use the defer utility
  • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
    • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
  • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

• Improve getDependenciesToBundle resolution in monorepos (#8848)
• Fix SPA mode when single fetch is enabled by using streaming entry.server (#9063)
• Vite: added sourcemap support for transformed routes (#8970)
• Update links printed to the console by the Remix CLI/Dev Server to point to updated docs locations (#9176)
• Updated dependencies:
  • @remix-run/node@2.9.0
  • @remix-run/server-runtime@2.9.0

@remix-run/node@2.9.0

Minor Changes

• Use undici as our fetch polyfill going forward. feat: use undici as fetch polyfill #9106 (#9111)

Patch Changes

• • Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#9198)
  • remix-serve will default to using undici for the fetch polyfill if future._unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
    • Any users opting into Single Fetch and managing their own polfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch
• Updated dependencies:
  • @remix-run/server-runtime@2.9.0

@remix-run/react@2.9.0

Minor Changes

• New future.unstable_singleFetch flag (#8773)

  • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
  • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
    • If you need to return a custom status code or custom response headers, you can still use the defer utility
  • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
    • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
  • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

• [REMOVE] Loosen header check on turbo stream responses for SSG compatibility (#9162)
• [REMOVE] bump router (#9289)
• fix: escape single fetch transfer (#9084)
• Update single fetch implementation to avoid over-fetching when clientLoader's exist (#9073)
• [REMOVE] Include future folder in published package (#9282)
• [REMOVE] Fix return type when no promise is used (194788b93)
• Opt-in types for single-fetch (#9272)
  • To opt-in to type inference for single-fetch, add ./node_modules/@remix-run/react/future/single-fetch.d.ts to include in your tsconfig.json
• Updated dependencies:
  • @remix-run/server-runtime@2.9.0

@remix-run/server-runtime@2.9.0

Minor Changes

• New future.unstable_singleFetch flag (#8773)

  • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
  • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
    • If you need to return a custom status code or custom response headers, you can still use the defer utility
  • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
    • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
  • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

• [REMOVE] Fix typings for response in LoaderFunctonArgs/ActionFunctionArgs (#9254)

• handle net new redirects created by handleDataRequest (#9104)

• [REMOVE] Remove RR flags and implement via dataStrategy (#9157)

• Add ResponseStub header interface for single fetch and deprecate the headers export (#9142)

  • The headers export is no longer used when single fetch is enabled
  • loader/action functions now receive a mutable response parameter
    • type ResponseStub = { status: numbers | undefined, headers: Headers }
  • To alter the status of a response, set the status field directly
    • response.status = 201
  • To set headers on the Response, you may use:
    • response.headers.set
    • response.headers.append
    • response.headers.delete
  • Each loader/actionreceives it's own unique response instance so you cannot see what other loader/action functions have set (which would be subject to race conditions)
  • If all status codes are unset or have values <200, the deepest status code will be used for the HTTP response
  • If any status codes are set to a value >=300, the highest >=300 value will be used for the HTTP Response
  • Remix tracks header operations and will replay them in order (action if present, then loaders top-down) after all handlers have completed on a fresh Headers instance that will be applied to the HTTP Response
    • headers.set on any child handler will overwrite values from parent handlers
    • headers.append can be used to set the same header from both a parent and child handler
    • headers.delete can be used to delete a value set by a parent handler, but not a value set from a child handler
  • Because single fetch supports naked object returns, and you no longer need to return a Response instance to set status/headers, the json/redirect/redirectDocument/defer utilities are considered deprecated when using Single Fetch
  • You may still continue returning normal Response instances and they'll apply status codes in the same way, and will apply all headers via headers.set - overwriting any same-named header values from parents
    • If you need to append, you will need to switch from returning a Response instance to using the new response parameter

@remix-run/testing@2.9.0

Minor Changes

• New future.unstable_singleFetch flag (#8773)

  • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
  • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
    • If you need to return a custom status code or custom response headers, you can still use the defer utility
  • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
    • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
  • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.9.0
  • @remix-run/react@2.9.0

create-remix@2.9.0

Patch Changes

• Allow . in repo name when using --template flag (#9026)

@remix-run/architect@2.9.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.9.0

@remix-run/cloudflare@2.9.0

Patch Changes

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

@remix-run/cloudflare-pages@2.9.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.9.0

@remix-run/cloudflare-workers@2.9.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.9.0

@remix-run/deno@2.9.0

Patch Changes

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

@remix-run/express@2.9.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.9.0

@remix-run/serve@2.9.0

Patch Changes

• • Put undici fetch polyfill behind a new installGlobals({ nativeFetch: true }) parameter (#9198)
  • remix-serve will default to using undici for the fetch polyfill if future._unstable_singleFetch is enabled because the single fetch implementation relies on the undici polyfill
    • Any users opting into Single Fetch and managing their own polfill will need to pass the flag to installGlobals on their own to avoid runtime errors with Single Fetch
• Updated dependencies:
  • @remix-run/node@2.9.0
  • @remix-run/express@2.9.0

remix@2.9.0

remix

See the CHANGELOG.md in individual Remix packages for all changes.

@remix-run/css-bundle@2.9.0

@remix-run/eslint-config@2.9.0