Bump @remix-run/react from 1.19.3 to 2.4.0

[dependabot]

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

Release notes

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

v2.4.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v240

v2.3.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v231

v2.3.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v230

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

... (truncated)

Changelog

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

2.4.0

Minor Changes

• Add support for clientLoader/clientAction/HydrateFallback route exports (RFC). (#8173)

  Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:

  • Leveraging a data source local to the browser (i.e., localStorage)
  • Managing a client-side cache of server data (like IndexedDB)
  • Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
  • Migrating a React Router SPA to a Remix application

  By default, clientLoader will not run on hydration, and will only run on subsequent client side navigations.

  If you wish to run your client loader on hydration, you can set clientLoader.hydrate=true to force Remix to execute it on initial page load. Keep in mind that Remix will still SSR your route component so you should ensure that there is no new required data being added by your clientLoader.

  If your clientLoader needs to run on hydration and adds data you require to render the route component, you can export a HydrateFallback component that will render during SSR, and then your route component will not render until the clientLoader has executed on hydration.

  clientAction is simpler than clientLoader because it has no hydration use-cases. clientAction will only run on client-side navigations.

  For more information, please refer to the clientLoader and clientAction documentation.

• Add a new future.v3_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. For more information, please see the React Router 6.21.0 Release Notes and the useResolvedPath docs. (#8216)

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]

2.3.1

Patch Changes

• Updated dependencies:
  • @remix-run/[email protected]

2.3.0

Minor Changes

• Remove the unstable_ prefix from the useBlocker hook as it's been in use for enough time that we are confident in the API. We do not plan to remove the prefix from unstable_usePrompt due to differences in how browsers handle window.confirm that prevent React Router from guaranteeing consistent/correct behavior. (#7882)

Patch Changes

• Support rendering of LiveReload component after Scripts in Vite dev (#7919)
• Support optional rendering of LiveReload component in Vite dev (#7919)
• add missing modulepreload for the manifest (#7684)
• Updated dependencies:
  • [email protected]

... (truncated)

Commits

• 82d03e8 chore: Update version for release (#8280)
• 6ca87ff chore: Update version for release (pre) (#8279)
• 2964cc8 Lock into stable router versions (#8277)
• 3a1a450 chore: Update version for release (pre) (#8276)
• 467db5b chore: Update version for release (pre) (#8254)
• 4fc551a Minor client data edge case fixes (#8253)
• 80a624b chore: Update version for release (pre) (#8249)
• d0eac1d chore: Update version for release (pre) (#8237)
• afa838f Minor client data implementation cleanups (#8236)
• 2639ede chore: Update version for release (pre) (#8234)
• 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]

The following labels could not be found: dependencies.

[dependabot]

Superseded by #259.