chore(deps): bump @remix-run/react from 1.19.3 to 2.2.0

[dependabot]

Bumps @remix-run/react from 1.19.3 to 2.2.0.

Release notes

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

v2.2.0

Minor Changes

Vite!

Remix 2.2.0 adds unstable support for Vite for Node-based apps! See our announcement blog post and the Future > Vite page in the Remix docs for more details. (#7590)

You can try it out today with two new (unstable) templates:

# minimal server
npx create-remix@latest --template remix-run/remix/templates/unstable-vite
custom server (Express example)
npx create-remix@latest --template remix-run/remix/templates/unstable-vite-express

New APIs in @remix-run/dev

• unstable_vitePlugin: The new Remix Vite plugin
• unstable_createViteServer: Creates a Vite server in middleware mode for interop with custom servers
• unstable_loadViteServerBuild: Allows your custom server to delegate SSR requests to Vite during development

Changed APIs

• createRequestHandler: Now also allows the build argument to be a function that will be used to dynamically load new builds for each request during development

Other Runtimes

• Deno support is untested, but should work through Deno's Node/npm interop
• CloudFlare support is not yet available

New Fetcher APIs

Per this RFC, we've introduced some new APIs that give you more granular control over your fetcher behaviors. (#10960)

• You may now specify your own fetcher identifier via useFetcher({ key: string }), which allows you to access the same fetcher instance from different components in your application without prop-drilling
• Fetcher keys are now exposed on the fetchers returned from useFetchers so that they can be looked up by key
• Form and useSumbit now support optional navigate/fetcherKey props/params to allow kicking off a fetcher submission under the hood with an optionally user-specified key
  • <Form method="post" navigate={false} fetcherKey="my-key">
  • submit(data, { method: "post", navigate: false, fetcherKey: "my-key" })
  • Invoking a fetcher in this way is ephemeral and stateless
  • If you need to access the state of one of these fetchers, you will need to leverage useFetchers() or useFetcher({ key }) to look it up elsewhere

Persistence Future Flag (future.v3_fetcherPersist)

Per the same RFC as above, we've introduced a new future.v3_fetcherPersist flag that allows you to opt-into the new fetcher persistence/cleanup behavior. Instead of being immediately cleaned up on unmount, fetchers will persist until they return to an idle state. This makes pending/optimistic UI much easier in scenarios where the originating fetcher needs to unmount. (#10962)

• This is sort of a long-standing bug fix as the useFetchers() API was always supposed to only reflect in-flight fetcher information for pending/optimistic UI -- it was not intended to reflect fetcher data or hang onto fetchers after they returned to an idle state
• Keep an eye out for the following specific behavioral changes when opting into this flag and check your app for compatibility:

... (truncated)

Changelog

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

2.2.0

Minor Changes

• Unstable Vite support for Node-based Remix apps (#7590)
  • remix build 👉 vite build && vite build --ssr
  • remix dev 👉 vite dev
  • Other runtimes (e.g. Deno, Cloudflare) not yet supported.
  • See "Future > Vite" in the Remix Docs for details
• Add a new future.v3_fetcherPersist flag to change the persistence behavior of fetchers. Instead of being immediately cleaned up when unmounted in the UI, fetchers will persist until they return to an idle state (RFC) (#7704)
  • For more details, please refer to the React Router 6.18.0 release notes

Patch Changes

• Fix warning that could be logged when using route files with no default export (#7745)
  • It seems our compiler compiles these files to export an empty object as the default which we can then end up passing to React.createElement, triggering the console warning, but generally no UI issues
  • By properly detecting these, we can correctly pass Component: undefined off to the React Router layer
  • This is technically an potential issue in the compiler but it's an easy patch in the @remix-run/react layer and hopefully disappears in a Vite world
• Fix critical CSS hydration errors for Vite dev (#7812)
• Updated dependencies:
  • @remix-run/[email protected]
  • [email protected]
  • @remix-run/[email protected]

2.1.0

Minor Changes

• Add experimental support for the View Transitions API via document.startViewTransition to enable CSS animated transitions on SPA navigations in your application (#7648)
  • For additional information please refer to the 2.1.0 Release Notes or the documentation

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]
  • [email protected]
  • @remix-run/[email protected]

2.0.1

Patch Changes

• Add second generic to UIMatch for handle field (#7464)
• Fix resource routes being loaded through route.lazy (#7498)

... (truncated)

Commits

• 85caf9b chore: Update version for release (#7841)
• 23bf4c8 chore: Update version for release (pre) (#7839)
• 332459d Bump to RR 6.18.0 (#7838)
• ccc77f5 chore: Update version for release (pre) (#7831)
• 754d6b8 chore: Update version for release (pre) (#7827)
• 0d01fbd Bump to latest router prerelease (#7825)
• 4841b62 chore: Update version for release (pre) (#7813)
• 28ac1db fix(react): fix Vite dev CSS hydration errors (#7812)
• aa8511e chore: Update version for release (pre) (#7780)
• f45986a Add fetcherKey APIs and update fetcher persistence architecture (#7704)
• 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)

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	fdf0af0
Status:	🚫  Build failed.

View logs

[dependabot]

Superseded by #201.