Bump react-router from 4.2.0 to 6.20.0

[dependabot]

Bumps react-router from 4.2.0 to 6.20.0.

Release notes

Sourced from react-router's releases.

v6.20.0

Release notes are stored in the CHANGELOG.md file:

https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6200

v6.19.0

Release notes are stored in the CHANGELOG.md file:

https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v6190

v6.18.0

Minor Changes

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

Per the same RFC as above, we've introduced a new future.v7_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:
  • Fetchers that complete while still mounted will no longer appear in useFetchers() after completion - they served no purpose in there since you can access the data via useFetcher().data
  • Fetchers that previously unmounted while in-flight will not be immediately aborted and will instead be cleaned up once they return to an idle state
    • They will remain exposed via useFetchers while in-flight so you can still access pending/optimistic data after unmount
    • If a fetcher is no longer mounted when it completes, then it's result will not be post processed - e.g., redirects will not be followed and errors will not bubble up in the UI
    • However, if a fetcher was re-mounted elsewhere in the tree using the same key, then it's result will be processed, even if the originating fetcher was unmounted

Other Minor Changes

• Add support for optional path segments in matchPath (#10768)

Patch Changes

• Fix the future prop on BrowserRouter, HashRouter and MemoryRouter so that it accepts a Partial<FutureConfig> instead of requiring all flags to be included (#10962)
• Fix router.getFetcher/router.deleteFetcher type definitions which incorrectly specified key as an optional parameter (#10960)

Full Changelog: 6.17.0...6.18.0

v6.17.0

Minor Changes

... (truncated)

Changelog

Sourced from react-router's changelog.

6.20.0

Minor Changes

• Export the PathParam type from the public API (#10719)

Patch Changes

• Fix bug with resolveTo in splat routes (#11045)
  • This is a follow up to #10983 to handle the few other code paths using getPathContributingMatches
  • This removes the UNSAFE_getPathContributingMatches export from @remix-run/router since we no longer need this in the react-router/react-router-dom layers
• Updated dependencies:
  • @remix-run/[email protected]

6.19.0

Minor Changes

• Add unstable_flushSync option to useNavigate/useSumbit/fetcher.load/fetcher.submit to opt-out of React.startTransition and into ReactDOM.flushSync for state updates (#11005)
• 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. (#10991)

Patch Changes

• Fix useActionData so it returns proper contextual action data and not any action data in the tree (#11023)

• Fix bug in useResolvedPath that would cause useResolvedPath(".") in a splat route to lose the splat portion of the URL path. (#10983)

  • ⚠️ This fixes a quite long-standing bug specifically for "." paths inside a splat route which incorrectly dropped the splat portion of the URL. If you are relative routing via "." inside a splat route in your application you should double check that your logic is not relying on this buggy behavior and update accordingly.

• Updated dependencies:

  • @remix-run/[email protected]

6.18.0

Patch Changes

• Fix the future prop on BrowserRouter, HashRouter and MemoryRouter so that it accepts a Partial<FutureConfig> instead of requiring all flags to be included. (#10962)
• Updated dependencies:
  • @remix-run/[email protected]

6.17.0

Patch Changes

• Fix RouterProvider future prop type to be a Partial<FutureConfig> so that not all flags must be specified (#10900)
• Updated dependencies:
  • @remix-run/[email protected]

6.16.0

Minor Changes

... (truncated)

Commits

• 3cc38ea chore: Update version for release (#11050)
• 1e026b6 chore: Update version for release (pre) (#11047)
• 58d421f Fix other code paths for resolveTo from a splat route (#11045)
• f320378 Add additional test case for #10983
• a48c43c feat: export PathParam type (#10719)
• dcf0c2a chore: Update version for release (#11035)
• 7b1bd10 chore: Update version for release (pre) (#11026)
• 39854ce Fix useAcrtionData so it only returns the contextual route action data (#11023)
• 1193ae5 Add unstable_flushSync option (#11005)
• fe066bd Fix issues with useFormAction/useResolvedPath for dot paths in param/splat ro...
• 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.