upd(deps): bump @remix-run/router from 1.15.3 to 1.19.1

[dependabot]

Bumps @remix-run/router from 1.15.3 to 1.19.1.

Changelog

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

1.19.1

Patch Changes

• Fog of War: Update unstable_patchRoutesOnMiss logic so that we call the method when we match routes with dynamic param or splat segments in case there exists a higher-scoring static route that we've not yet discovered. (#11883)

  • We also now leverage an internal FIFO queue of previous paths we've already called unstable_patchRouteOnMiss against so that we don't re-call on subsequent navigations to the same path

• Rename unstable_patchRoutesOnMiss to unstable_patchRoutesOnNavigation to match new behavior (#11888)

1.19.0

Minor Changes

• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#11811)
• Add a new unstable_data() API for usage with Remix Single Fetch (#11836)
  • This API is not intended for direct usage in React Router SPA applications
  • It is primarily intended for usage with createStaticHandler.query() to allow loaders/actions to return arbitrary data + status/headers without forcing the serialization of data into a Response instance
  • This allows for more advanced serialization tactics via unstable_dataStrategy such as serializing via turbo-stream in Remix Single Fetch
  • ⚠️ This removes the status field from HandlerResult
    • If you need to return a specific status from unstable_dataStrategy you should instead do so via unstable_data()

Patch Changes

• Fix internal cleanup of interrupted fetchers to avoid invalid revalidations on navigations (#11839)
  • When a fetcher.load is interrupted by an action submission, we track it internally and force revalidation once the action completes
  • We previously only cleared out this internal tracking info on a successful navigation submission
  • Therefore, if the fetcher.load was interrupted by a fetcher.submit, then we wouldn't remove it from this internal tracking info on successful load (incorrectly)
  • And then on the next navigation it's presence in the internal tracking would automatically trigger execution of the fetcher.load again, ignoring any shouldRevalidate logic
  • This fix cleans up the internal tracking so it applies to both navigation submission and fetcher submissions
• Fix initial hydration behavior when using future.v7_partialHydration along with unstable_patchRoutesOnMiss (#11838)
  • During initial hydration, router.state.matches will now include any partial matches so that we can render ancestor HydrateFallback components

1.18.0

Minor Changes

• Stabilize future.unstable_skipActionErrorRevalidation as future.v7_skipActionErrorRevalidation (#11769)
  • When this flag is enabled, actions will not automatically trigger a revalidation if they return/throw a Response with a 4xx/5xx status code
  • You may still opt-into revalidation via shouldRevalidate
  • This also changes shouldRevalidate's unstable_actionStatus parameter to actionStatus

Patch Changes

• Fix bubbling of errors thrown from unstable_patchRoutesOnMiss (#11786)
• Fix hydration in SSR apps using unstable_patchRoutesOnMiss that matched a splat route on the server (#11790)

1.17.1

Patch Changes

... (truncated)

Commits

• 04d09c3 chore: Update version for release (#11895)
• f806fa4 chore: Update version for release (pre) (#11889)
• 5a6545b Rename patchRoutesOnMiss to patchRoutesOnNavigation (#11888)
• bd4ac8e Call patchRoutesOnMiss when matching slug routes in case there exist higher s...
• 91ef146 chore: Update version for release (#11863)
• 7acbfbe chore: Update version for release (pre) (#11860)
• 6263aa2 Export DataWithResponseInit type for Remix usage (#11859)
• 8334033 chore: Update version for release (pre) (#11854)
• ecdbbde Fix fetcher interruption cleanup logic after fetcher submissions (#11839)
• 653d1a8 Fix hydration behavior of patchRoutesOnMiss when v7_partialHydration is enabl...
• 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)