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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@remix-run/dev (source)	2.4.0 -> 2.8.1
@remix-run/react (source)	2.4.0 -> 2.8.1

---

Release Notes

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

v2.8.1

Compare Source

Patch Changes

• Support reading from Vite config when running remix reveal and remix routes CLI commands (#​8916)
• Add Vite commands to Remix CLI --help output (#​8939)
• Vite: Fix support for build.sourcemap option in Vite config (#​8965)
• Clean up redundant client route query strings on route JavaScript files in production builds (#​8969)
• Vite: Fix error when using Vite's server.fs.allow option without a client entry file (#​8966)
• Updated dependencies:
  • @remix-run/node@2.8.1
  • @remix-run/server-runtime@2.8.1

v2.8.0

Compare Source

Minor Changes

• Pass resolved viteConfig to Remix Vite plugin's buildEnd hook (#​8885)

Patch Changes

• Mark Layout as browser safe route export in esbuild compiler (#​8842)
• Vite: Silence build warnings when dependencies include "use client" directives (#​8897)
• Vite: Fix serverBundles issue where multiple browser manifests are generated (#​8864)
• Support custom Vite build.assetsDir option (#​8843)
• Updated dependencies:
  • @remix-run/node@2.8.0
  • @remix-run/server-runtime@2.8.0

v2.7.2

Compare Source

Patch Changes

• Vite: Fix error when building projects with .css?url imports (#​8829)
• Updated dependencies:
  • @remix-run/node@2.7.2
  • @remix-run/server-runtime@2.7.2

v2.7.1

Compare Source

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.7.1
  • @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: Cloudflare Proxy as a Vite plugin (#​8749)

  This is a breaking change for projects relying on Cloudflare support from the unstable Vite plugin

  The Cloudflare preset (unstable_cloudflarePreset) as been removed and replaced with a new Vite plugin:

   import {
      unstable_vitePlugin as remix,
  -   unstable_cloudflarePreset as cloudflare,
  +   cloudflareDevProxyVitePlugin as remixCloudflareDevProxy,
    } from "@​remix-run/dev";
    import { defineConfig } from "vite";
  
    export default defineConfig({
      plugins: [
  +     remixCloudflareDevProxy(),
  +     remix(),
  -     remix({
  -       presets: [cloudflare()],
  -     }),
      ],
  -   ssr: {
  -     resolve: {
  -       externalConditions: ["workerd", "worker"],
  -     },
  -   },
    });

  remixCloudflareDevProxy must come before the remix plugin so that it can override Vite's dev server middleware to be compatible with Cloudflare's proxied environment.

  Because it is a Vite plugin, remixCloudflareDevProxy can set ssr.resolve.externalConditions to be workerd-compatible for you.

  remixCloudflareDevProxy accepts a getLoadContext function that replaces the old getRemixDevLoadContext.
  If you were using a nightly version that required getBindingsProxy or getPlatformProxy, that is no longer required.
  Any options you were passing to getBindingsProxy or getPlatformProxy should now be passed to remixCloudflareDevProxy instead.

  This API also better aligns with future plans to support Cloudflare with a framework-agnostic Vite plugin that makes use of Vite's (experimental) Runtime API.

• Vite: Stabilize the Remix Vite plugin, Cloudflare preset, and all related types by removing all unstable_ / Unstable_ prefixes. (#​8713)

  While this is a breaking change for existing Remix Vite plugin consumers, now that the plugin has stabilized, there will no longer be any breaking changes outside of a major release. Thank you to all of our early adopters and community contributors for helping us get here! 🙏

• Vite: Stabilize "SPA Mode" by renaming the Remix vite plugin config from unstable_ssr -> ssr (#​8692)

• 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

• Vite: fix server exports dead-code elimination for routes outside of app directory (#​8795)

• Always prepend DOCTYPE in SPA mode entry.server.tsx, can opt out via remix reveal (#​8725)

• Fix build issue in SPA mode when using a basename (#​8720)

• Vite: Validate that the MDX Rollup plugin, if present, is placed before Remix in Vite config (#​8690)

• Vite: reliably detect non-root routes in Windows (#​8806)

  Sometimes route file will be unnormalized Windows path with \ instead of /.

• Vite: Pass remixUserConfig to preset remixConfig hook (#​8797)

• Vite: Fix issue resolving critical CSS during development when the current working directory differs from the project root (#​8752)

• Vite: Ensure CSS file URLs that are only referenced in the server build are available on the client (#​8796)

• Vite: Require version 5.1.0 to support .css?url imports (#​8723)

• Fix type error in Remix config for synchronous routes function (#​8745)

• Vite: Support Vite v5.1.0's .css?url imports (#​8684)

• Always ignore route files starting with . (#​8801)

• Vite: Enable use of vite preview to preview Remix SPA applications (#​8624)

  • In the SPA template, npm run start has been renamed to npm run preview which uses vite preview instead of a standalone HTTP server such as http-server or serv-cli

• Vite: Remove the ability to pass publicPath as an option to the Remix vite plugin (#​8145)

  • ⚠️ This is a breaking change for projects using the unstable Vite plugin with a publicPath
  • This is already handled in Vite via the base config so we now set the Remix publicPath from the Vite base config

• Vite: Fix issue where client route file requests fail if search params have been parsed and serialized before reaching the Remix Vite plugin (#​8740)

• Vite: Enable HMR for .md and .mdx files (#​8711)

• Updated dependencies:

  • @remix-run/server-runtime@2.7.0
  • @remix-run/node@2.7.0

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/server-runtime@2.6.0
  • @remix-run/node@2.6.0

v2.5.1

Compare Source

Patch Changes

• Add isSpaMode to @remix-run/dev/server-build virtual module (#​8492)
• Automatically prepend <!DOCTYPE html> if not present to fix quirks mode warnings for SPA template (#​8495)
• Vite: Errors for server-only code point to new docs (#​8488)
• Vite: Fix HMR race condition when reading changed file contents (#​8479)
• Vite: Tree-shake unused route exports in the client build (#​8468)
• Vite: Performance profiling (#​8493)
  • Run remix vite:build --profile to generate a .cpuprofile that can be shared or uploaded to speedscope.app
  • In dev, press p + enter to start a new profiling session or stop the current session
  • If you need to profile dev server startup, run remix vite:dev --profile to initialize the dev server with a running profiling session
  • For more, see the new docs: Vite > Performance
• Vite: Improve performance of dev server requests by invalidating Remix's virtual modules on relevant file changes rather than on every request (#​8164)
• Updated dependencies:
  • @remix-run/node@2.5.1
  • @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.

• Add unstable_serverBundles option to Vite plugin to support splitting server code into multiple request handlers. (#​8332)

  This is an advanced feature designed for hosting provider integrations. When compiling your app into multiple server bundles, there will need to be a custom routing layer in front of your app directing requests to the correct bundle. This feature is currently unstable and only designed to gather early feedback.

  Example usage:

  import { unstable_vitePlugin as remix } from "@​remix-run/dev";
  import { defineConfig } from "vite";
  
  export default defineConfig({
    plugins: [
      remix({
        unstable_serverBundles: ({ branch }) => {
          const isAuthenticatedRoute = branch.some(
            (route) => route.id === "routes/_authenticated"
          );
  
          return isAuthenticatedRoute ? "authenticated" : "unauthenticated";
        },
      }),
    ],
  });

Patch Changes

• Fix issue with isbot v4 released on 1/1/2024 (#​8415)

  • remix dev will now add "isbot": "^4" to package.json instead of using latest
  • Update built-in entry.server files to work with both isbot@3 and isbot@4 for backwards-compatibility with Remix apps that have pinned isbot to v3
  • Templates are updated to use isbot@4 moving forward via create-remix

• Vite: Fix HMR issues when altering exports for non-rendered routes (#​8157)

• Vite: Default NODE_ENV to "production" when running remix vite:build command (#​8405)

• Vite: Remove Vite plugin config option serverBuildPath in favor of separate serverBuildDirectory and serverBuildFile options (#​8332)

• Vite: Loosen strict route exports restriction, reinstating support for non-Remix route exports (#​8420)

• Updated dependencies:

  • @remix-run/server-runtime@2.5.0
  • @remix-run/node@2.5.0

v2.4.1

Compare Source

Patch Changes

• Vite: Error messages when .server files are referenced by client (#​8267)

  • Previously, referencing a .server module from client code resulted in an error message like:
    • The requested module '/app/models/answer.server.ts' does not provide an export named 'isDateType'
  • This was confusing because answer.server.ts does provide the isDateType export, but Remix was replacing .server modules with empty modules (export {}) for the client build
  • Now, Remix explicitly fails at compile time when a .server module is referenced from client code and includes dedicated error messages depending on whether the import occurs in a route or a non-route module
  • The error messages also include links to relevant documentation

• Remove unstable_viteServerBuildModuleId in favor of manually referencing virtual module name "virtual:remix/server-build". (#​8264)

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

  This change was made to avoid issues where @remix-run/dev could be inadvertently required in your server's production dependencies.

  Instead, you should manually write the virtual module name "virtual:remix/server-build" when calling ssrLoadModule in development.

  -import { unstable_viteServerBuildModuleId } from "@​remix-run/dev";
  
  // ...
  
  app.all(
    "*",
    createRequestHandler({
      build: vite
  -      ? () => vite.ssrLoadModule(unstable_viteServerBuildModuleId)
  +      ? () => vite.ssrLoadModule("virtual:remix/server-build")
        : await import("./build/server/index.js"),
    })
  );

• Vite: Fix errors for non-existent index.html importer (#​8353)

• Add vite:dev and vite:build commands to the Remix CLI. (#​8211)

  In order to handle upcoming Remix features where your plugin options can impact the number of Vite builds required, you should now run your Vite dev and build processes via the Remix CLI.

  {
    "scripts": {
  -    "dev": "vite dev",
  -    "build": "vite build && vite build --ssr"
  +    "dev": "remix vite:dev",
  +    "build": "remix vite:build"
    }
  }

• Vite: Preserve names for exports from .client modules (#​8200)

  Unlike .server modules, the main idea is not to prevent code from leaking into the server build
  since the client build is already public. Rather, the goal is to isolate the SSR render from client-only code.
  Routes need to import code from .client modules without compilation failing and then rely on runtime checks
  or otherwise ensure that execution only happens within a client-only context (e.g. event handlers, useEffect).

  Replacing .client modules with empty modules would cause the build to fail as ESM named imports are statically analyzed.
  So instead, we preserve the named export but replace each exported value with undefined.
  That way, the import is valid at build time and standard runtime checks can be used to determine if the
  code is running on the server or client.

• Disable watch mode in Vite child compiler during build (#​8342)

• Vite: Show warning when source maps are enabled in production build (#​8222)

• Updated dependencies:

  • @remix-run/server-runtime@2.4.1
  • @remix-run/node@2.4.1

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

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

v2.4.1

Compare Source

Patch Changes

• Propagate server loader errors through serverLoader in hydrating clientLoader's (#​8304)
• Re-export Response helpers (defer/json/redirect/redirectDocument) through @remix-run/react for use in clientLoader/clientAction (#​8351)
• Updated dependencies:
  • @remix-run/server-runtime@2.4.1

---

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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@remix-run/dev@2.8.1	environment, filesystem Transitive: eval, network, shell, unsafe	+217	455 MB	mjackson
npm/@remix-run/react@2.8.1	environment, network	+5	3.07 MB	mjackson

🚮 Removed packages: npm/@remix-run/dev@2.4.0, npm/@remix-run/react@2.4.0

View full report↗︎