chore: Update version for release (pre)

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

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@remix-run/dev@2.5.0-pre.0

Minor Changes

• 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";
        },
      }),
    ],
  });

• 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][https://reactrouter.com/en/main/guides/spa-mode].

Patch Changes

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

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

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

  • remix dev wil 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

• Updated dependencies:

  • @remix-run/serve@2.5.0-pre.0
  • @remix-run/server-runtime@2.5.0-pre.0
  • @remix-run/node@2.5.0-pre.0

@remix-run/react@2.5.0-pre.0

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][https://reactrouter.com/en/main/guides/spa-mode].

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-pre.0

@remix-run/server-runtime@2.5.0-pre.0

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][https://reactrouter.com/en/main/guides/spa-mode].

@remix-run/testing@2.5.0-pre.0

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][https://reactrouter.com/en/main/guides/spa-mode].

Patch Changes

• Updated dependencies:
  • @remix-run/react@2.5.0-pre.0
  • @remix-run/node@2.5.0-pre.0

create-remix@2.5.0-pre.0

Patch Changes

• Only update * versions for Remix dependencies (#8458)

@remix-run/architect@2.5.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.5.0-pre.0

@remix-run/cloudflare@2.5.0-pre.0

Patch Changes

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

@remix-run/cloudflare-pages@2.5.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.5.0-pre.0

@remix-run/cloudflare-workers@2.5.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.5.0-pre.0

@remix-run/deno@2.5.0-pre.0

Patch Changes

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

@remix-run/express@2.5.0-pre.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.5.0-pre.0

@remix-run/node@2.5.0-pre.0

Patch Changes

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

@remix-run/serve@2.5.0-pre.0

Patch Changes

• Don't try to load sourcemaps if they don't exist on disk (#8446)
• Updated dependencies:
  • @remix-run/node@2.5.0-pre.0
  • @remix-run/express@2.5.0-pre.0

remix@2.5.0-pre.0

remix

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

@remix-run/css-bundle@2.5.0-pre.0

@remix-run/eslint-config@2.5.0-pre.0