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

build(deps): bump the remix group with 4 updates #336

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 30, 2024

Bumps the remix group with 4 updates: @remix-run/node, @remix-run/react, @remix-run/serve and @remix-run/dev.

Updates @remix-run/node from 2.11.2 to 2.12.1

Release notes

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

v2.12.1

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

v2.12.0

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

Changelog

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

2.12.1

Patch Changes

  • Single Fetch: Re-export interface Future through @remix-run/node/@remix-run/cloudflare/@remix-run/deno packages so that pnpm doesn't complain about @remix-run/server-runtime not being a dependency (#9982)
  • Updated dependencies:

2.12.0

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:

Commits

Updates @remix-run/react from 2.11.2 to 2.12.1

Release notes

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

v2.12.1

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

v2.12.0

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

Changelog

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

2.12.1

Patch Changes

2.12.0

Patch Changes

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

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

    • Reverts the logic originally added in Remix v1.18.0 via remix-run/remix#6409
    • This was added to resolve an issue that could arise when doing quick back/forward history navigations while JS was loading which would cause a mismatch between the server matches and client matches: remix-run/remix#1757
    • This specific hydration issue would then cause this React v17 only looping issue: remix-run/remix#1678
    • The URL comparison that we added in 1.18.0 turned out to be subject to false positives of it's own which could also put the user in looping scenarios
    • Remix v2 upgraded it's minimal React version to v18 which eliminated the v17 hydration error loop
    • React v18 handles this hydration error like any other error and does not result in a loop
    • So we can remove our check and thus avoid the false-positive scenarios in which it may also trigger a loop
  • 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

... (truncated)

Commits

Updates @remix-run/serve from 2.11.2 to 2.12.1

Release notes

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

v2.12.1

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

v2.12.0

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

Changelog

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

2.12.1

Patch Changes

2.12.0

Patch Changes

Commits

Updates @remix-run/dev from 2.11.2 to 2.12.1

Release notes

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

v2.12.1

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

v2.12.0

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

Changelog

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

2.12.1

Patch Changes

  • Properly abort request.signal during vite dev when the node response is closed (#9976)
  • CSS imports with ?inline, ?inline-css and ?raw are no longer incorrectly injected during SSR in development (#9910)
  • Updated dependencies:

2.12.0

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:
Commits

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 30, 2024
Copy link

vercel bot commented Sep 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
content-collections ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 7, 2024 7:01pm

Copy link

changeset-bot bot commented Sep 30, 2024

⚠️ No Changeset found

Latest commit: 4dbf37b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

pkg-pr-new bot commented Sep 30, 2024

Open in Stackblitz

@content-collections/cli

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/cli@336

@content-collections/core

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/core@336

@content-collections/markdown

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/markdown@336

@content-collections/integrations

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/integrations@336

@content-collections/mdx

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/mdx@336

@content-collections/next

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/next@336

@content-collections/remix-vite

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/remix-vite@336

@content-collections/solid-start

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/solid-start@336

@content-collections/vite

pnpm add https://pkg.pr.new/sdorra/content-collections/@content-collections/vite@336

commit: 6ee8865

Bumps the remix group with 4 updates: [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node), [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react), [@remix-run/serve](https://github.com/remix-run/remix/tree/HEAD/packages/remix-serve) and [@remix-run/dev](https://github.com/remix-run/remix/tree/HEAD/packages/remix-dev).


Updates `@remix-run/node` from 2.11.2 to 2.12.1
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-node/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/[email protected]/packages/remix-node)

Updates `@remix-run/react` from 2.11.2 to 2.12.1
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-react/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/[email protected]/packages/remix-react)

Updates `@remix-run/serve` from 2.11.2 to 2.12.1
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-serve/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/[email protected]/packages/remix-serve)

Updates `@remix-run/dev` from 2.11.2 to 2.12.1
- [Release notes](https://github.com/remix-run/remix/releases)
- [Changelog](https://github.com/remix-run/remix/blob/main/packages/remix-dev/CHANGELOG.md)
- [Commits](https://github.com/remix-run/remix/commits/@remix-run/[email protected]/packages/remix-dev)

---
updated-dependencies:
- dependency-name: "@remix-run/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/react"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/serve"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: remix
- dependency-name: "@remix-run/dev"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: remix
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 14, 2024

Superseded by #351.

@dependabot dependabot bot closed this Oct 14, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/remix-ebc174100f branch October 14, 2024 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants