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

[dependabot]

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

Release notes

Sourced from @​remix-run/server-runtime'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/server-runtime'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

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";

... (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)
• a71411b fix(server-runtime): mark critical CSS arg private (#7814)
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.