chore(deps): update remix monorepo to ^2.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/dev (source)	^2.5.1 -> ^2.6.0
@remix-run/eslint-config (source)	^2.5.1 -> ^2.6.0
@remix-run/node (source)	^2.5.1 -> ^2.6.0
@remix-run/react (source)	^2.5.1 -> ^2.6.0
@remix-run/serve (source)	^2.5.1 -> ^2.6.0

---

Release Notes

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

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: Add manifest option to Vite plugin to enable writing a .remix/manifest.json file to the build directory (#​8575)

  This is a breaking change for consumers of the Vite plugin's "server bundles" feature.

  The build/server/bundles.json file has been superseded by the more general build/.remix/manifest.json. While the old server bundles manifest was always written to disk when generating server bundles, the build manifest file must be explicitly enabled via the manifest option.

• Vite: Provide Unstable_ServerBundlesFunction and Unstable_VitePluginConfig types (#​8654)

• Vite: add --sourcemapClient and --sourcemapServer flags to remix vite:build (#​8613)

  • --sourcemapClient

  • --sourcemapClient=inline

  • --sourcemapClient=hidden

  • --sourcemapServer

  • --sourcemapServer=inline

  • --sourcemapServer=hidden

  See https://vitejs.dev/config/build-options.html#build-sourcemap

• Vite: Validate IDs returned from the serverBundles function to ensure they only contain alphanumeric characters, hyphens and underscores (#​8598)

• Vite: fix "could not fast refresh" false alarm (#​8580)

  HMR is already functioning correctly but was incorrectly logging that it "could not fast refresh" on internal client routes.
  Now internal client routes correctly register Remix exports like meta for fast refresh,
  which removes the false alarm.

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

• Vite: Remove undocumented backwards compatibility layer for Vite v4 (#​8581)

• Vite: rely on Vite plugin ordering (#​8627)

  This is a breaking change for projects using the unstable Vite plugin.

  The Remix plugin expects to process JavaScript or TypeScript files, so any transpilation from other languages must be done first.
  For example, that means putting the MDX plugin before the Remix plugin:

    import mdx from "@​mdx-js/rollup";
    import { unstable_vitePlugin as remix } from "@​remix-run/dev";
    import { defineConfig } from "vite";
  
    export default defineConfig({
      plugins: [
  +     mdx(),
        remix()
  -     mdx(),
      ],
    });

  Previously, the Remix plugin misused enforce: "post" from Vite's plugin API to ensure that it ran last.
  However, this caused other unforeseen issues.
  Instead, we now rely on standard Vite semantics for plugin ordering.

  The official Vite React SWC plugin also relies on plugin ordering for MDX.

• Vite: Add presets option to ease integration with different platforms and tools. (#​8514)

• Vite: Remove interop with <LiveReload />, rely on <Scripts /> instead (#​8636)

  This is a breaking change for projects using the unstable Vite plugin.

  Vite provides a robust client-side runtime for development features like HMR,
  making the <LiveReload /> component obsolete.

  In fact, having a separate dev scripts component was causing issues with script execution order.
  To work around this, the Remix Vite plugin used to override <LiveReload /> into a bespoke
  implementation that was compatible with Vite.

  Instead of all this indirection, now the Remix Vite plugin instructs the <Scripts /> component
  to automatically include Vite's client-side runtime and other dev-only scripts.

    import {
  -   LiveReload,
      Outlet,
      Scripts,
    }
  
    export default function App() {
      return (
        <html>
          <head>
          </head>
          <body>
            <Outlet />
            <Scripts />
  -         <LiveReload />
          </body>
        </html>
      )
    }

• Vite: Add buildEnd hook (#​8620)

• Vite: add dev load context option to Cloudflare preset (#​8649)

• Vite: Add mode field into generated server build (#​8539)

• Vite: Only write Vite manifest files if build.manifest is enabled within the Vite config (#​8599)

  This is a breaking change for consumers of Vite's manifest.json files.

  To explicitly enable generation of Vite manifest files, you must set build.manifest to true in your Vite config.

  export default defineConfig({
    build: { manifest: true },
    // ...
  });

• Vite: reduce network calls for route modules during HMR (#​8591)

• Vite: Add new buildDirectory option with a default value of "build". This replaces the old assetsBuildDirectory and serverBuildDirectory options which defaulted to "build/client" and "build/server" respectively. (#​8575)

  This is a breaking change for consumers of the Vite plugin that were using the assetsBuildDirectory and serverBuildDirectory options.

  The Remix Vite plugin now builds into a single directory containing client and server directories. If you've customized your build output directories, you'll need to migrate to the new buildDirectory option, e.g.

  import { unstable_vitePlugin as remix } from "@​remix-run/dev";
  import { defineConfig } from "vite";
  
  export default defineConfig({
    plugins: [
      remix({
  -      serverBuildDirectory: "dist/server",
  -      assetsBuildDirectory: "dist/client",
  +      buildDirectory: "dist",
      })
    ],
  });

• Vite: Remove unstable prefix from serverBundles option. (#​8596)

• Vite: Write Vite manifest files to build/.vite directory rather than being nested within build/client and build/server directories. (#​8599)

  This is a breaking change for consumers of Vite's manifest.json files.

  Vite manifest files are now written to the Remix build directory. Since all Vite manifests are now in the same directory, they're no longer named manifest.json. Instead, they're named build/.vite/client-manifest.json and build/.vite/server-manifest.json, or build/.vite/server-{BUNDLE_ID}-manifest.json when using server bundles.

• Updated dependencies:

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

remix-run/remix (@​remix-run/eslint-config)

v2.6.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.6.0.

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

v2.6.0

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]

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

v2.6.0

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]

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

v2.6.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: 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.

[netlify]

✅ Deploy Preview for brilliant-pasca-3e80ec canceled.

Name	Link
🔨 Latest commit	b2fef9b
🔍 Latest deploy log	https://app.netlify.com/sites/brilliant-pasca-3e80ec/deploys/65bcb31c7ea4f60008a0d70c