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

create-remix@2.4.1

Patch Changes

• Switch to using @remix-run/web-fetch instead of node-fetch inside the create-remix CLI (#7345)

@remix-run/architect@2.4.1

Patch Changes

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

@remix-run/cloudflare@2.4.1

Patch Changes

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

@remix-run/cloudflare-pages@2.4.1

Patch Changes

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

@remix-run/cloudflare-workers@2.4.1

Patch Changes

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

@remix-run/deno@2.4.1

Patch Changes

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

@remix-run/dev@2.4.1

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/express@2.4.1

Patch Changes

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

@remix-run/node@2.4.1

Patch Changes

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

@remix-run/react@2.4.1

Patch Changes

• [REMOVE] Bunmp to stable RR (#8348)
• Propagate server loader errors through serverLoader in hydrating clientLoader's (#8304)
• [REMOVE] Bump router (#8346)
• 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

@remix-run/serve@2.4.1

Patch Changes

• Use node fileURLToPath to convert source map URL to path (#8321)
• Updated dependencies:
  • @remix-run/node@2.4.1
  • @remix-run/express@2.4.1

@remix-run/server-runtime@2.4.1

Patch Changes

• Add optional error to ServerRuntimeMetaArgs type to align with MetaArgs (#8238)

@remix-run/testing@2.4.1

Patch Changes

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

remix@2.4.1

remix

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

@remix-run/css-bundle@2.4.1

@remix-run/eslint-config@2.4.1