Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update version for release #8486

Merged
merged 2 commits into from
Jan 11, 2024

Conversation

github-actions[bot]
Copy link
Contributor

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

@remix-run/[email protected]

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://remix.run/future/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 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
    • [REMOVE] Error if no <Scripts> included in root <HydrateFallback> (#8464)
    • [REMOVE] Don't render SSR scroll restoration script in SPA mode
  • Updated dependencies:

@remix-run/[email protected]

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://remix.run/future/spa-mode].

Patch Changes

    • [REMOVE] Error if no <Scripts> included in root <HydrateFallback> (#8464)
    • [REMOVE] Don't render SSR scroll restoration script in SPA mode
  • Vite: Fix type conflict with import.meta.hot from the existing Remix compiler (#8459)
  • [REMOVE] Bump router to stable (#8484)
  • Updated dependencies:

@remix-run/[email protected]

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://remix.run/future/spa-mode].

@remix-run/[email protected]

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://remix.run/future/spa-mode].

Patch Changes

[email protected]

Patch Changes

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

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

[email protected]

remix

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

@remix-run/[email protected]

@remix-run/[email protected]

@brophdawg11 brophdawg11 merged commit d88606e into release-next Jan 11, 2024
9 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch January 11, 2024 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant