chore(deps): update remix monorepo to v2.9.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/node (source)	2.4.1 -> 2.9.2
@remix-run/react (source)	2.4.1 -> 2.9.2
@remix-run/server-runtime (source)	2.4.1 -> 2.9.2

---

Release Notes

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

v2.9.2

Compare Source

Patch Changes

• Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
• Updated dependencies:
  • @remix-run/server-runtime@2.9.2

v2.9.1

Compare Source

Patch Changes

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

v2.9.0

Compare Source

Minor Changes

• Use undici as our fetch polyfill going forward (#​9106, #​9111)
• 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

Patch Changes

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

v2.8.1

Compare Source

Patch Changes

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

v2.8.0

Compare Source

Patch Changes

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

v2.7.2

Compare Source

Patch Changes

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

v2.7.1

Compare Source

Patch Changes

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

v2.7.0

Compare Source

Patch Changes

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

v2.6.0

Compare Source

Patch Changes

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

v2.5.1

Compare Source

Patch Changes

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

v2.5.0

Compare Source

Patch Changes

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

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

v2.9.2

Compare Source

Patch Changes

• Add undefined to useActionData type override (#​9322)
• Allow a nonce to be set on single fetch stream transfer inline scripts (#​9364)
• Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
• Updated dependencies:
  • @remix-run/server-runtime@2.9.2

v2.9.1

Compare Source

Patch Changes

• Ignore future/*.d.ts files from TS build (#​9299)
• Updated dependencies:
  • @remix-run/server-runtime@2.9.1

v2.9.0

Compare Source

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

• 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

Patch Changes

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

v2.8.1

Compare Source

Patch Changes

• Strengthen the internal LayoutComponent type to accept limited children (#​8910)
• Updated dependencies:
  • @remix-run/server-runtime@2.8.1

v2.8.0

Compare Source

Patch Changes

• Fix the default root ErrorBoundary component so it leverages the user-provided Layout component (#​8859)
• Fix the default root HydrateFallback component so it leverages any user-provided Layout component (#​8892)
• Ensure @remix-run/react re-exports everything from react-router-dom for SPA mode (#​8929)
• Updated dependencies:
  • @remix-run/server-runtime@2.8.0

v2.7.2

Compare Source

Patch Changes

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

v2.7.1

Compare Source

Patch Changes

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

v2.7.0

Compare Source

Minor Changes

• Allow an optional Layout export from the root route (#​8709)
• Vite: Add a new basename option to the Vite plugin, allowing users to set the internal React Router basename in order to to serve their applications underneath a subpath (#​8145)

Patch Changes

• [REMOVE] Bump router (#​8771)
• Fix a bug with SPA mode when the root route had no children (#​8747)
• [REMOVE] Bump RR version (#​8774)
• Updated dependencies:
  • @remix-run/server-runtime@2.7.0

v2.6.0

Compare Source

Patch Changes

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

v2.5.1

Compare Source

Patch Changes

• Only use active matches in <Meta>/<Links> in SPA mode (#​8538)
• Remove leftover unstable_ prefix from Blocker/BlockerFunction types (#​8530)
• Updated dependencies:
  • @remix-run/server-runtime@2.5.1

v2.5.0

Compare Source

Minor Changes

• Add unstable support for "SPA Mode" (#​8457)

  You can opt into SPA Mode by setting unstable_ssr: false in your Remix Vite plugin config:

  // vite.config.ts
  import { unstable_vitePlugin as remix } from "@​remix-run/dev";
  import { defineConfig } from "vite";
  
  export default defineConfig({
    plugins: [remix({ unstable_ssr: false })],
  });

  Development in SPA Mode is just like a normal Remix app, and still uses the Remix dev server for HMR/HDR:

  remix vite:dev

  Building in SPA Mode will generate an index.html file in your client assets directory:

  remix vite:build

  To run your SPA, you serve your client assets directory via an HTTP server:

  npx http-server build/client

  For more information, please refer to the SPA Mode docs.

Patch Changes

• Vite: Fix type conflict with import.meta.hot from the existing Remix compiler (#​8459)
• Updated dependencies:
  • @remix-run/server-runtime@2.5.0

remix-run/remix (@​remix-run/server-runtime)

v2.9.2

Compare Source

Patch Changes

• Don't log thrown response stubs via handleError in Single Fetch (#​9369)
• Automatically wrap resource route naked object returns in json() for back-compat in v2 (and log deprecation warning) (#​9349)
• Typesafety for single-fetch: defineLoader, defineClientLoader, defineAction, defineClientAction (#​9372, #​9404)
• Pass response stub to resource route handlers when single fetch is enabled (#​9349)

v2.9.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.9.1.

v2.9.0

Compare Source

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

Patch Changes

• Handle net new redirects created by handleDataRequest (#​9104)

v2.8.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.1.

v2.8.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.8.0.

v2.7.2

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.7.2.

v2.7.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.7.1.

v2.7.0

Compare Source

Minor Changes

• Allow an optional Layout export from the root route (#​8709)
• Vite: Add a new basename option to the Vite plugin, allowing users to set the internal React Router basename in order to to serve their applications underneath a subpath (#​8145)

Patch Changes

• Add a more specific error if a user returns a defer response from a resource route (#​8726)

v2.6.0

Compare Source

Minor Changes

• Add future.v3_throwAbortReason flag to throw request.signal.reason when a request is aborted instead of an Error such as new Error("query() call aborted: GET /path") (#​8251)

Patch Changes

• Vite: Cloudflare Pages support (#​8531)

  To get started with Cloudflare, you can use the [unstable-vite-cloudflare][template-vite-cloudflare] template:

  npx create-remix@latest --template remix-run/remix/templates/unstable-vite-cloudflare
  

  Or read the new docs at Future > Vite > Cloudflare and
  Future > Vite > Migrating > Migrating Cloudflare Functions.

• Unwrap thrown Response's from entry.server into ErrorResponse's and preserve the status code (#​8577)

v2.5.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.5.1.

v2.5.0

Compare Source

Minor Changes

• Updated cookie dependency to 0.6.0 to inherit support for the Partitioned attribute (#​8375)

• Add unstable support for "SPA Mode" (#​8457)

  You can opt into SPA Mode by setting unstable_ssr: false in your Remix Vite plugin config:

  // vite.config.ts
  import { unstable_vitePlugin as remix } from "@​remix-run/dev";
  import { defineConfig } from "vite";
  
  export default defineConfig({
    plugins: [remix({ unstable_ssr: false })],
  });

  Development in SPA Mode is just like a normal Remix app, and still uses the Remix dev server for HMR/HDR:

  remix vite:dev

  Building in SPA Mode will generate an index.html file in your client assets directory:

  remix vite:build

  To run your SPA, you serve your client assets directory via an HTTP server:

  npx http-server build/client

  For more information, please refer to the SPA Mode docs.

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 57e12c4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: remix-auth-spotify@1.3.2
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   dev react@"18.2.0" from the root project
npm ERR!   peer react@"^18.0.0" from @remix-run/react@2.9.2
npm ERR!   node_modules/@remix-run/react
npm ERR!     dev @remix-run/react@"2.9.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.3.1" from react-dom@18.3.1
npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@"^18.0.0" from @remix-run/react@2.9.2
npm ERR!   node_modules/@remix-run/react
npm ERR!     dev @remix-run/react@"2.9.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-10T21_17_29_537Z-debug-0.log