Bump the frontends-dev group across 1 directory with 2 updates

[dependabot]

Bumps the frontends-dev group with 2 updates in the /client directory: @vitejs/plugin-react and sass.

Updates @vitejs/plugin-react from 5.1.1 to 5.1.2

Changelog

Sourced from @​vitejs/plugin-react's changelog.

5.1.2 (2025-12-08)

Commits

• f127a24 release: [email protected]
• db1c665 fix(react): newer full bundle mode compat (#1011)
• 1f372b6 fix(deps): update all non-major dependencies (#1008)
• d52455e fix(deps): update react 19.2.1 (#998)
• bcda041 fix(deps): update all non-major dependencies (#995)
• c80546d fix(deps): update all non-major dependencies (#982)
• See full diff in compare view

Updates sass from 1.94.2 to 1.95.0

Release notes

Sourced from sass's releases.

Dart Sass 1.95.0

To install Sass 1.95.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Add support for the CSS-style if() function. In addition to supporting the plain CSS syntax, this also supports a sass() query that takes a Sass expression that evaluates to true or false at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3) returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special variable strings" (like var()), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.

See the full changelog for changes in earlier releases.

Dart Sass 1.94.3

To install Sass 1.94.3, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Fix the span reported for standalone % expressions followed by whitespace.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.95.0

• Add support for the CSS-style if() function. In addition to supporting the plain CSS syntax, this also supports a sass() query that takes a Sass expression that evaluates to true or false at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3) returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special variable strings" (like var()), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.

1.94.3

• Fix the span reported for standalone % expressions followed by whitespace.

Commits

• 2abc89e Merge pull request #2693 from sass/css-if
• 2f7a16c Revert "Bump chokidar from 4.0.3 to 5.0.0 in /package (#2690)" (#2691)
• 38d4ac8 Add ArgumentList.namedSpans
• 6f9a593 Add support for plain-CSS if()
• 3b95eb7 Rename IfExpression to LegacyIfExpression
• e2bf843 Make the recursive AST visitor comprehensive (#2694)
• 9380924 Fix the operator span when parsing a standalone % (#2667)
• f8a8a51 Bump chokidar from 4.0.3 to 5.0.0 in /package (#2690)
• e4837d1 Bump archive from 3.6.1 to 4.0.7 (#2688)
• 293200b Bump protoc_plugin from 23.0.0 to 24.0.0 (#2677)
• 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 <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