Bump the frontend group in /web with 10 updates

[dependabot]

Bumps the frontend group in /web with 10 updates:

Package	From	To
react-router-dom	6.20.0	6.21.0
@testing-library/jest-dom	6.1.4	6.1.5
@types/jest	29.5.10	29.5.11
@types/node	20.10.0	20.10.5
@types/react	18.2.38	18.2.45
@types/react-dom	18.2.17	18.2.18
eslint-config-prettier	9.0.0	9.1.0
postcss	8.4.31	8.4.32
prettier	3.1.0	3.1.1
typescript	5.3.2	5.3.3

Updates react-router-dom from 6.20.0 to 6.21.0

Release notes

Sourced from react-router-dom's releases.

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• Updated dependencies
  • [email protected]
  • [email protected]

[email protected]

Patch Changes

• 44bce3c6: Fix react-router-dom peer dependency version
  • [email protected]
  • [email protected]

[email protected]

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.21.0

Minor Changes

• Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#11087)

  This fix was originally added in #10983 and was later reverted in #11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #11052)

  The Bug The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

  The Background This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

  <BrowserRouter>
    <Routes>
      <Route path="/" element={<Home />} />
      <Route path="dashboard/*" element={<Dashboard />} />
    </Routes>
  </BrowserRouter>

  Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

  function Dashboard() {
    return (
      <div>
        <h2>Dashboard</h2>
        <nav>
          <Link to="/">Dashboard Home</Link>
          <Link to="team">Team</Link>
          <Link to="projects">Projects</Link>
        </nav>
    &lt;Routes&gt;
      &lt;Route path=&quot;/&quot; element={&lt;DashboardHome /&gt;} /&gt;
      &lt;Route path=&quot;team&quot; element={&lt;DashboardTeam /&gt;} /&gt;
      &lt;Route path=&quot;projects&quot; element={&lt;DashboardProjects /&gt;} /&gt;
    &lt;/Routes&gt;
  &lt;/div&gt;
  
  );
  }

  Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

  The Problem

... (truncated)

Commits

• 69ba50e chore: Update version for release (#11114)
• ea0ffee chore: Update version for release (pre) (#11095)
• fe3c071 Slight refactor to partial hydration to leverage state.initialized properly (...
• 373b30c chore: Update version for release (pre) (#11091)
• f9d7ed6 Fix server future plumbing
• 56b2944 chore: Update version for release (pre) (#11090)
• 558d793 Fix plumbing of future prop
• ee5fcd5 Generate release notes
• ddc2b94 chore: Update version for release (pre) (#11089)
• 149ad65 Add future.v7_relativeSplatPath flag (#11087)
• Additional commits viewable in compare view

Updates @testing-library/jest-dom from 6.1.4 to 6.1.5

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.1.5

6.1.5 (2023-11-30)

Bug Fixes

• support uppercase custom props in toHaveStyle (#552) (b7b7c6a)

Commits

• b7b7c6a fix: support uppercase custom props in toHaveStyle (#552)
• 4ae0231 docs: Add missing hr to README.md (#550)
• See full diff in compare view

Updates @types/jest from 29.5.10 to 29.5.11

Commits

• See full diff in compare view

Updates @types/node from 20.10.0 to 20.10.5

Commits

• See full diff in compare view

Updates @types/react from 18.2.38 to 18.2.45

Commits

• See full diff in compare view

Updates @types/react-dom from 18.2.17 to 18.2.18

Commits

• See full diff in compare view

Updates eslint-config-prettier from 9.0.0 to 9.1.0

Changelog

Sourced from eslint-config-prettier's changelog.

Version 9.1.0 (2023-12-02)

• Added: [unicorn/template-indent], (as a [special rule][unicorn/template-indent-special]). Thanks to Gürgün Dayıoğlu (@​gurgunday)!
• Changed: All the [formatting rules that were deprecated in ESLint 8.53.0][deprecated-8.53.0] are now excluded if you set the ESLINT_CONFIG_PRETTIER_NO_DEPRECATED environment variable.

Commits

• 40c7f3d eslint-config-prettier v9.1.0
• 4110dff Merge pull request #271 from prettier/deprecated
• 6d0bd92 Update tests to handle newly deprecated rules
• 4c876b9 Move rules deprecated in ESLint 8.53.0 to the deprecated section
• 24445c0 Use specialRule constant
• 7827196 Group deprecated and removed rules by version
• 48f804c Roll back to ESLint 8.52.0 for now
• 16f03b8 Update Prettier
• b06d618 Update npm packages
• 25fc427 turn off unicorn/template-indent (#269)
• Additional commits viewable in compare view

Updates postcss from 8.4.31 to 8.4.32

Release notes

Sourced from postcss's releases.

8.4.32

• Fixed postcss().process() types (by @​ferreira-tb).

Changelog

Sourced from postcss's changelog.

8.4.32

• Fixed postcss().process() types (by Andrew Ferreira).

Commits

• a0d9f10 Release 8.4.32 version
• 0146b3e Add Node.js 21 to CI
• 2398534 Update dependencies
• 1918533 Merge pull request #1902 from ferreira-tb/main
• 395e6dc Fix ProcessOptions interface
• fa8cd15 Update dependencies
• 199a7c4 Typo
• 2528047 Update EM link
• See full diff in compare view

Updates prettier from 3.1.0 to 3.1.1

Release notes

Sourced from prettier's releases.

3.1.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.1.1

diff

Fix config file search (#15363 by @​fisker)

Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.

├─ .prettierrc
└─ test.js         (A directory)
  └─ .prettierrc

// Prettier 3.1.0
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/test.js/.prettierrc
// Prettier 3.1.1
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/.prettierrc

Skip explicitly passed symbolic links with --no-error-on-unmatched-pattern (#15533 by @​sanmai-NL)

Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.

In Prettier 3.1.1, you can use --no-error-on-unmatched-pattern to simply skip symbolic links.

Consistently use tabs in ternaries when useTabs is true (#15662 by @​auvred)

// Input
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;
// Prettier 3.1.0
aaaaaaaaaaaaaaa
? bbbbbbbbbbbbbbbbbb
: ccccccccccccccc
? ddddddddddddddd
: eeeeeeeeeeeeeee
? fffffffffffffff
</tr></table>

... (truncated)

Commits

• b86701d Release 3.1.1
• c97480c Use attributes instead of deprecated assertions (#15758)
• 0d1ffb3 Consistently use tabs in ternaries when useTabs is true (#15662)
• 5f7aedc fix example to fit the actual experimentalTernaries behaviour (#15747)
• 1e30f66 Remove claim, untrue since over 5 years ago, that cursorOffset is incompatibl...
• 39e4e7b Add cursorOffset to Playground (#15751)
• 8e816ad Allow skipping symlink patterns, to avoid raising a fault (#15533)
• 2ca5d75 Fix expect call in dts test (#15766)
• 15c7428 chore(deps): update dependency flow-parser to v0.223.3 (#15760)
• d3b3d4f chore(deps): update dependency hermes-parser to v0.18.0 (#15761)
• Additional commits viewable in compare view

Updates typescript from 5.3.2 to 5.3.3

Release notes

Sourced from typescript's releases.

TypeScript 5.3.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.3.0 (Beta).
• fixed issues query for Typescript 5.3.1 (RC).
• fixed issues query for Typescript 5.3.2 (Stable).
• fixed issues query for Typescript 5.3.3 (Stable).

Downloads are available on:

• NuGet package

Commits

• 63717cf Bump version to 5.3.3 and LKG
• 4c2afa7 🤖 Pick PR #56627 (Transpile jsdoc parsing mode) into release-5.3 (#56629)
• ba3d2b0 🤖 Pick PR #56434 (Fix support for intersections in te...) into release-5.3 (#...
• f3808c4 🤖 Pick PR #56504 (Fixed an issue in boolean compariso...) into release-5.3 (#...
• b4fe221 Cherry-pick #56489 into release-5.3 (#56490)
• f750eb3 Pick #56485 into release-5.3 (#56486)
• 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.