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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update remix monorepo to v2.14.0 #5683

Merged
merged 1 commit into from
Nov 17, 2024
Merged

fix(deps): update remix monorepo to v2.14.0 #5683

merged 1 commit into from
Nov 17, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@remix-run/cloudflare (source) 2.12.1 -> 2.14.0 age adoption passing confidence
@remix-run/cloudflare-pages (source) 2.12.1 -> 2.14.0 age adoption passing confidence
@remix-run/css-bundle (source) 2.12.1 -> 2.14.0 age adoption passing confidence
@remix-run/dev (source) 2.12.1 -> 2.14.0 age adoption passing confidence
@remix-run/react (source) 2.12.1 -> 2.14.0 age adoption passing confidence

Release Notes

remix-run/remix (@​remix-run/cloudflare)

v2.14.0

Compare Source

Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Patch Changes
remix-run/remix (@​remix-run/cloudflare-pages)

v2.14.0

Compare Source

Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Patch Changes
remix-run/remix (@​remix-run/css-bundle)

v2.14.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.14.0.

v2.13.1

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.1.

v2.13.0

Compare Source

No significant changes to this package were made in this release. See the repo CHANGELOG.md for an overview of all changes in v2.13.0.

remix-run/remix (@​remix-run/dev)

v2.14.0

Compare Source

Minor Changes

  • Add support for routes.ts behind future.unstable_routeConfig flag to assist with the migration to React Router v7. (#​10107)

    Config-based routing is the new default in React Router v7, configured via the routes.ts file in the app directory. Support for routes.ts and its related APIs in Remix are designed as a migration path to help minimize the number of changes required when moving your Remix project over to React Router v7. While some new packages have been introduced within the @remix-run scope, these new packages only exist to keep the code in routes.ts as similar as possible to the equivalent code for React Router v7.

    When the unstable_routeConfig future flag is enabled, Remix's built-in file system routing will be disabled and your project will opted into React Router v7's config-based routing.

    To enable the flag, in your vite.config.ts file:

    remix({
  future: {
    unstable_routeConfig: true,
  },
});

    A minimal routes.ts file to support Remix's built-in file system routing looks like this:

    // app/routes.ts
import { flatRoutes } from "@​remix-run/fs-routes";
import type { RouteConfig } from "@​remix-run/route-config";

export const routes: RouteConfig = flatRoutes();

  • Log deprecation warnings for v3 future flags (#​10126)

    • Add @deprecated annotations to json/defer utilities
Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Minor Changes
  • Stabilize the future.unstable_optimizeDeps flag into future.v3_optimizeDeps (#​10092)
  • Stabilize React Router APIs in Remix (#​9980)
    • Adopt stabilized React Router APIs internally
      • Single Fetch: unstable_dataStrategy -> dataStrategy
      • Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
    • Stabilize public-facing APIs
      • Single Fetch: unstable_data() -> data()
      • unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
      • unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
  • Stabilize future flags (#​10072)
    • future.unstable_singleFetch -> future.v3_singleFetch
    • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery
Patch Changes

  • Stop passing request.signal as the renderToReadableStream signal to abort server rendering for cloudflare/deno runtimes because by the time that request is aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#​10047)

    • This has been incorrect for some time, but only recently exposed due to a bug in how we were aborting requests when running via remix vite:dev because we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closed ReadableStream.
    • This has likely not shown up in any production scenarios because cloudflare/deno production runtimes are (correctly) not aborting the request.signal on successful renders
    • The built-in entry.server files no longer pass a signal to renderToReadableStream because adding a timeout-based abort signal to the default behavior would constitute a breaking change
    • Users can configure this abort behavior via their own entry.server via remix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix apps

  • Fix adapter logic for aborting request.signal so we don't incorrectly abort on the close event for successful requests (#​10046)

  • Updated dependencies:

remix-run/remix (@​remix-run/react)

v2.14.0

Compare Source

Patch Changes

v2.13.1

Compare Source

Patch Changes

v2.13.0

Compare Source

Minor Changes
  • Stabilize React Router APIs in Remix (#​9980)
    • Adopt stabilized React Router APIs internally
      • Single Fetch: unstable_dataStrategy -> dataStrategy
      • Lazy Route Discovery: unstable_patchRoutesOnNavigation -> patchRoutesOnNavigation
    • Stabilize public-facing APIs
      • Single Fetch: unstable_data() -> data()
      • unstable_viewTransition -> viewTransition (Link, Form, navigate, submit)
      • unstable_flushSync> -> <Link viewTransition> (Link, Form, navigate, submit, useFetcher)
  • Stabilize future flags (#​10072)
    • future.unstable_singleFetch -> future.v3_singleFetch
    • future.unstable_lazyRouteDiscovery -> future.v3_lazyRouteDiscovery
Patch Changes
  • Fix bug with clientLoader.hydrate in a layout route when hydrating with bubbled errors (#​10063)
  • Updated dependencies:

Configuration

📅 Schedule: Branch creation - "after 5:00am every weekday, before 7:00am every weekday,every weekend" (UTC), Automerge - "before 7am every weekday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner November 17, 2024 06:26
@renovate renovate bot enabled auto-merge (squash) November 17, 2024 06:26
@renovate renovate bot requested review from aqrln and millsp and removed request for a team November 17, 2024 06:26
@renovate renovate bot merged commit 6e9f51c into dev Nov 17, 2024
3 checks passed
@renovate renovate bot deleted the renovate/remix-monorepo branch November 17, 2024 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@aqrln aqrln Awaiting requested review from aqrln aqrln is a code owner automatically assigned from prisma/orm-ts-maintain

@millsp millsp Awaiting requested review from millsp millsp is a code owner automatically assigned from prisma/orm-ts-maintain

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants