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 (pre) #7655

Merged
merged 1 commit into from
Oct 12, 2023

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.

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@remix-run/[email protected]

Minor Changes

  • Add support for the View Transitions API via document.startViewTransition to enable CSS animated transitions on SPA navigations in your application. (#7648)

    The simplest approach to enabling a View Transition in your Remix app is via the new <Link unstable_viewTransition> prop. This will cause the navigation DOM update to be wrapped in document.startViewTransition which will enable transitions for the DOM update. Without any additional CSS styles, you'll get a basic cross-fade animation for your page.

    If you need to apply more fine-grained styles for your animations, you can leverage the unstable_useViewTransitionState hook which will tell you when a transition is in progress and you can use that to apply classes or styles:

    function ImageLink(to, src, alt) {
      let isTransitioning = unstable_useViewTransitionState(to);
      return (
        <Link to={to} unstable_viewTransition>
          <img
            src={src}
            alt={alt}
            style={{
              viewTransitionName: isTransitioning ? "image-expand" : "",
            }}
          />
        </Link>
      );
    }

    You can also use the <NavLink unstable_viewTransition> shorthand which will manage the hook usage for you and automatically add a transitioning class to the <a> during the transition:

    a.transitioning img {
      view-transition-name: "image-expand";
    }
    <NavLink to={to} unstable_viewTransition>
      <img src={src} alt={alt} />
    </NavLink>

    For more information on using the View Transitions API, please refer to the Smooth and simple transitions with the View Transitions API guide from the Google Chrome team.

Patch Changes

  • Avoid mutating meta object when tagName is specified (#7594)

  • Fix FOUC on subsequent client-side navigations to route.lazy routes (#7576)

  • Emulate types for JSON.parse(JSON.stringify(x)) in SerializeFrom (#7605)

    Notably, type fields that are only assignable to undefined after serialization are now omitted since
    JSON.stringify |> JSON.parse will omit them. See test cases for examples.

    Also fixes type errors when upgrading to v2 from 1.19

  • Export the proper Remix useMatches wrapper to fix UIMatch typings (#7551)

  • Updated dependencies:

@remix-run/[email protected]

Minor Changes

  • Remove the unstable_ prefix from createRemixStub. After real-world experience, we're confident in the API and ready to commit to it. (#7647)
    • Note: This involves 1 small breaking change. The <RemixStub remixConfigFuture> prop has been renamed to <RemixStub future>

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

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Emulate types for JSON.parse(JSON.stringify(x)) in SerializeFrom (#7605)

    Notably, type fields that are only assignable to undefined after serialization are now omitted since
    JSON.stringify |> JSON.parse will omit them. See test cases for examples.

    Also fixes type errors when upgrading to v2 from 1.19

[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 b4cd467 into release-next Oct 12, 2023
1 check passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch October 12, 2023 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant