Bump the all group in /app-frontend with 5 updates

[dependabot]

Bumps the all group in /app-frontend with 5 updates:

Package	From	To
core-js	3.33.1	3.33.2
react-router	6.17.0	6.18.0
react-router-dom	6.17.0	6.18.0
@types/node	20.8.9	20.8.10
@types/react	18.2.33	18.2.35

Updates core-js from 3.33.1 to 3.33.2

Changelog

Sourced from core-js's changelog.

3.33.2 - 2023.10.31

• Simplified structuredClone polyfill, avoided second tree pass in cases of transferring
• Added support of SuppressedError to structuredClone polyfill
• Removed unspecified unnecessary ArrayBuffer and DataView dependencies of structuredClone lack of which could cause errors in some entries in IE10-
• Fixed handling of fractional number part in Number.fromString
• Compat data improvements:
  • URL.canParse marked as supported from Chromium 120
  • Updated Opera Android 78 compat data mapping
  • Added Electron 29 compat data mapping

Commits

• 7cbd6b5 3.33.2
• ffc6984 temporarily drop unspecified special cases from Number.fromString before cl...
• f7b095e fix handling of fractional number part and some special cases in `Number.from...
• 55cd424 adapt get-built-in-prototype-method helper for some future use cases
• effda0c drop an extra method name
• d6f71d1 add support of SuppressedError to structuredClone polyfill and simplify it
• c6ea9f7 simplify structuredClone polyfill, avoid second tree pass in cases of trans...
• 65e9213 remove unspecified unnecessary ArrayBuffer and DataView dependencies of `...
• See full diff in compare view

Updates react-router from 6.17.0 to 6.18.0

Release notes

Sourced from react-router's releases.

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

Changelog

Sourced from react-router's changelog.

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/router@1.11.0

Commits

• 667f936 chore: Update version for release (#10981)
• 67af262 chore: Update version for release (pre) (#10978)
• cacc90b chore: Update version for release (pre) (#10966)
• 19af0cf Add future.v7_fetcherPersist flag (#10962)
• 677d6c8 Support optional path segments in matchPath (#10768)
• a71b4e2 Merge branch 'release-next' into dev
• e2c0d82 Split up router-test.ts (#10929)
• e74b935 Fix lint errors
• See full diff in compare view

Updates react-router-dom from 6.17.0 to 6.18.0

Release notes

Sourced from react-router-dom's releases.

react-router-dom-v5-compat@6.4.0-pre.15

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.15
  • react-router-dom@6.4.0-pre.15

react-router-dom-v5-compat@6.4.0-pre.11

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.11
  • react-router-dom@6.4.0-pre.11

react-router-dom-v5-compat@6.4.0-pre.10

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.10
  • react-router-dom@6.4.0-pre.10

react-router-dom-v5-compat@6.4.0-pre.9

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.9
  • react-router-dom@6.4.0-pre.9

react-router-dom-v5-compat@6.4.0-pre.8

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.8
  • react-router-dom@6.4.0-pre.8

react-router-dom-v5-compat@6.4.0-pre.7

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.7
  • react-router-dom@6.4.0-pre.7

react-router-dom-v5-compat@6.4.0-pre.6

Patch Changes

• 44bce3c6: Fix react-router-dom peer dependency version
  • react-router@6.4.0-pre.6
  • react-router-dom@6.4.0-pre.6

react-router-dom-v5-compat@6.4.0-pre.5

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.18.0

Minor Changes

• Add support for manual fetcher key specification via useFetcher({ key: string }) so you can access the same fetcher instance from different components in your application without prop-drilling (RFC) (#10960)

  • Fetcher keys are now also exposed on the fetchers returned from useFetchers so that they can be looked up by key

• Add navigate/fetcherKey params/props to useSumbit/Form to support kicking off a fetcher submission under the hood with an optionally user-specified key (#10960)

  • 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 useFetcher({ key }) to look it up elsewhere

Patch Changes

• Adds a fetcher context to RouterProvider that holds completed fetcher data, in preparation for the upcoming future flag that will change the fetcher persistence/cleanup behavior (#10961)
• 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/router@1.11.0
  • react-router@6.18.0

Commits

• 667f936 chore: Update version for release (#10981)
• 67af262 chore: Update version for release (pre) (#10978)
• 1500288 Updates for v7_fetcherPersist post-processing logic (#10977)
• cacc90b chore: Update version for release (pre) (#10966)
• 19af0cf Add future.v7_fetcherPersist flag (#10962)
• cb2d911 Add fetcher data layer (#10961)
• c0dbcd2 Add useFetcher(key) and <Form navigate={false}> (#10960)
• 805924d Revert "Ensure Form contains splat portion of pathname when no action is spec...
• 908a40a Ensure Form contains splat portion of pathname when no action is specified (#...
• a71b4e2 Merge branch 'release-next' into dev
• Additional commits viewable in compare view

Updates @types/node from 20.8.9 to 20.8.10

Commits

• See full diff in compare view

Updates @types/react from 18.2.33 to 18.2.35

Commits

• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions