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 #9965

Merged
merged 2 commits into from
Sep 9, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 9, 2024

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

  • New future.unstable_optimizeDeps flag for automatic dependency optimization (#9921)

    You can now opt-in to automatic dependency optimization during development by using the future.unstable_optimizeDeps future flag.
    For details, check out the docs at Guides > Dependency optimization.

    For users who were previously working around this limitation, you no longer need to explicitly add routes to Vite's optimizeDeps.entries nor do you need to disable the remix-dot-server plugin.

Patch Changes

  • Handle circular dependencies in modulepreload manifest generation. (#9917)
  • Fix dest already exists build errors by only moving SSR assets to the client build directory when they're not already present on disk (#9901)
  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Single Fetch: Improved typesafety (#9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Single Fetch: Improved typesafety (#9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Single Fetch: Improved typesafety (#9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

  • Lazy Route Discovery: Sort /__manifest query parameters for better caching (#9888)

  • [REMOVE] cleanup tests (#9945)

  • Single Fetch: fix revalidation behavior bugs (#9938)

    • With Single Fetch, existing routes revalidate by default
    • This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
    • There are two conditions that will trigger granular revalidation:
      • If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
      • If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
    • When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
      • For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a
  • [REMOVE] Align single fetch prefetchign with new revalidation logic (#9958)

  • Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)

  • [REMOVE] Bump router (#9963)

  • Single Fetch: Improved typesafety (#9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • [REMOVE] Fix HDR for single fetch (#9954)

  • Clarify wording in default HydrateFallback console warning (#9899)

  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Single Fetch: Do not try to encode a turbo-stream body into 304 responses (#9941)

  • Single Fetch: fix revalidation behavior bugs (#9938)

    • With Single Fetch, existing routes revalidate by default
    • This means requests do not need special query params for granular route revalidations out of the box - i.e., GET /a/b/c.data
    • There are two conditions that will trigger granular revalidation:
      • If a route opts out of revalidation via shouldRevalidate, it will be excluded from the single fetch call
      • If a route defines a clientLoader then it will be excluded from the single fetch call and if you call serverLoader() from your clientLoader, that will make a separarte HTTP call for just that route loader - i.e., GET /a/b/c.data?_routes=routes/a for a clientLoader in routes/a.tsx
    • When one or more routes are excluded from the single fetch call, the remaining routes that have loaders are included as query params:
      • For example, if A was excluded, and the root route and routes/b had a loader but routes/c did not, the single fetch request would be GET /a/b/c.data?_routes=root,routes/a
  • Remove hydration URL check that was originally added for React 17 hydration issues and we no longer support React 17 (#9890)

  • Single Fetch: Improved typesafety (#9893)

    If you were already using previously released unstable single-fetch types:

    • Remove "@remix-run/react/future/single-fetch.d.ts" override from tsconfig.json > compilerOptions > types
    • Remove defineLoader, defineAction, defineClientLoader, defineClientAction helpers from your route modules
    • Replace UIMatch_SingleFetch type helper with UIMatch
    • Replace MetaArgs_SingleFetch type helper with MetaArgs

    Then you are ready for the new typesafety setup:

    // vite.config.ts
    
    declare module "@remix-run/server-runtime" {
      interface Future {
        unstable_singleFetch: true; // 👈 enable _types_ for single-fetch
      }
    }
    
    export default defineConfig({
      plugins: [
        remix({
          future: {
            unstable_singleFetch: true, // 👈 enable single-fetch
          },
        }),
      ],
    });

    For more information, see Guides > Single Fetch in our docs.

  • Single Fetch: Change content type on .data requests to text/x-script to allow Cloudflare compression (#9889)

  • Support 304 responses on document requests (#9955)

@remix-run/[email protected]

Patch Changes

[email protected]

[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 e947032 into release-next Sep 9, 2024
9 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch September 9, 2024 17:33
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