Bump @remix-run/server-runtime from 1.19.3 to 2.1.0

[dependabot]

Bumps @remix-run/server-runtime from 1.19.3 to 2.1.0.

Release notes

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

v2.1.0

Minor Changes

View Transitions 🚀

We're excited to release experimental support for the the View Transitions API in Remix! You can now trigger navigational DOM updates to be wrapped in document.startViewTransition to enable CSS animated transitions on SPA navigations in your application. (#10916)

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) {
  const 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 an example usage of View Transitions, check out our fork of the Astro Records demo (which uses React Router but so does Remix 😉).

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.

Stable createRemixStub 🔒

After real-world experience, we're confident in the createRemixStub API and ready to commit to it, so in 2.1.0 we've removed the unstable_ prefix. (#7647)

... (truncated)

Changelog

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

2.1.0

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

2.0.1

No significant changes to this package were made in this release. See the releases page on GitHub for an overview of all changes in v2.0.1.

2.0.0

Major Changes

• Require Node >=18.0.0 (#6939)

• The route meta API now defaults to the new "V2 Meta" API (#6958)

  • Please refer to the (docs and Preparing for V2 guide for more information.

• Promote the future.v2_dev flag in remix.config.js to a root level dev config (#7002)

• Remove v2_errorBoundary flag and CatchBoundary implementation (#6906)

• Remove v2_normalizeFormMethod future flag - all formMethod values will be normalized in v2 (#6875)

• Remove v2_routeConvention flag - the flat route file convention is now standard (#6969)

• Remove v2_headers flag - it is now the default behavior to use the deepest headers function in the route tree (#6979)

• Remove imagesizes & imagesrcset properties from HtmlLinkDescriptor, LinkDescriptor & PrefetchPageDescriptor types (#6936)

• Removed/adjusted types to prefer unknown over any and to align with underlying React Router types (#7319, #7354):

  • Renamed the useMatches() return type from RouteMatch to UIMatch
  • Renamed LoaderArgs/ActionArgs to LoaderFunctionArgs/ActionFunctionArgs
  • AppData changed from any to unknown
  • Location["state"] (useLocation.state) changed from any to unknown
  • UIMatch["data"] (useMatches()[i].data) changed from any to unknown
  • UIMatch["handle"] (useMatches()[i].handle) changed from { [k: string]: any } to unknown
  • Fetcher["data"] (useFetcher().data) changed from any to unknown
  • MetaMatch.handle (used in meta()) changed from any to unknown
  • AppData/RouteHandle are no longer exported as they are just aliases for unknown

• Remove deprecated REMIX_DEV_HTTP_ORIGIN env var - use REMIX_DEV_ORIGIN instead (#6963)

• Removed support for "magic exports" from the remix package. This package can be removed from your package.json and you should update all imports to use the source @remix-run/* packages: (#6895)

  - import type { ActionArgs } from "remix";
  - import { json, useLoaderData } from "remix";
  + import type { ActionArgs } from "@remix-run/node";
  + import { json } from "@remix-run/node";
  + import { useLoaderData } from "@remix-run/react";

Minor Changes

• Update Remix to use React Router route.lazy for module loading (#7133)
• Detect built mode via build.mode (#6964)

... (truncated)

Commits

• 4c1047d chore: Update version for release (#7679)
• 31ce2a3 chore: Update version for release (pre) (#7678)
• 283631c Lock into stable react router version (#7677)
• b4cd467 chore: Update version for release (pre) (#7655)
• 5f175cd Add startViewTransition support (#7648)
• 7eeaa77 Reimplement Jsonify type utility (#7605)
• 27ee4fc chore: Update version for release (#7511)
• 7611467 chore: Update version for release (pre) (#7508)
• 65d36b8 Merge branch 'release-next' into dev
• e547efd chore: Update version for release (#7430)
• Additional commits viewable in compare view

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