storyblok / remix-ultimate-tutorial

7 stars 3 forks source link

chore(deps-dev): bump @remix-run/dev from 2.3.1 to 2.5.0 #26

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps @remix-run/dev from 2.3.1 to 2.5.0.

Release notes

Sourced from @​remix-run/dev's releases.

v2.5.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v250

v2.4.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v241

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

Changelog

Sourced from @​remix-run/dev's changelog.

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

  • 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: [

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 10 months ago

Superseded by #33.