[Tech] Bump the non-major-dev-dependencies group in /frontend with 8 updates

[dependabot]

Bumps the non-major-dev-dependencies group in /frontend with 8 updates:

Package	From	To
@swc/core	1.7.21	1.7.22
@types/ramda	0.30.1	0.30.2
@types/react	18.3.4	18.3.5
cypress	13.14.0	13.14.1
esbuild	0.23.0	0.23.1
eslint-plugin-jest	28.8.0	28.8.1
husky	9.1.4	9.1.5
type-fest	4.23.0	4.26.0

Updates @swc/core from 1.7.21 to 1.7.22

Changelog

Sourced from @​swc/core's changelog.

[1.7.22] - 2024-08-30

Bug Fixes

• (es/minifier) Iterate object properties in reverse direction while inlining property access (#9507) (f584ef7)

Commits

• 6290dd3 chore: Publish 1.7.22 with swc_core v0.102.2
• 2c505bf chore: Update changelog
• 4313e27 chore: Publish 1.7.22-nightly-20240830.1 with swc_core v0.102.2
• d0dd531 chore: Publish crates with swc_core v0.102.2
• 222aca1 chore: Enable html publish pipeline
• f584ef7 fix(es/minifier): Iterate object properties in reverse direction while inlini...
• 8c0d79d chore: Update changelog
• See full diff in compare view

Updates @types/ramda from 0.30.1 to 0.30.2

Commits

• See full diff in compare view

Updates @types/react from 18.3.4 to 18.3.5

Commits

• See full diff in compare view

Updates cypress from 13.14.0 to 13.14.1

Release notes

Sourced from cypress's releases.

v13.14.1

Changelog: https://docs.cypress.io/guides/references/changelog#13-14-1

Commits

• e909c4a chore: release 13.14.1 (#30138)
• 58abe80 chore: Update Chrome (stable) to 128.0.6613.113 (#30133)
• f6e7af9 fix: adds a description for the JIT experiment which was overlooked on initia...
• 0f77220 chore: fix kitchen sink running against staging to properly upload protocol d...
• d83b9a0 chore: release @​cypress/webpack-dev-server-v3.11.0
• bebb403 chore: release @​cypress/vite-dev-server-v5.2.0
• See full diff in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• See full diff in compare view

Updates eslint-plugin-jest from 28.8.0 to 28.8.1

Release notes

Sourced from eslint-plugin-jest's releases.

v28.8.1

28.8.1 (2024-08-29)

Bug Fixes

• prefer-importing-jest-globals: support typescript-eslint parser (#1639) (307f6a7)

Changelog

Sourced from eslint-plugin-jest's changelog.

28.8.1 (2024-08-29)

Bug Fixes

• prefer-importing-jest-globals: support typescript-eslint parser (#1639) (307f6a7)

Commits

• 1df45e9 chore(release): 28.8.1 [skip ci]
• 307f6a7 fix(prefer-importing-jest-globals): support typescript-eslint parser (#1639)
• 267702d chore(deps): lock file maintenance
• f969f92 chore(deps): lock file maintenance
• f5f3e99 chore(deps): lock file maintenance
• See full diff in compare view

Updates husky from 9.1.4 to 9.1.5

Release notes

Sourced from husky's releases.

v9.1.5

What's Changed

• fixes #1494, support pre-merge-commit hook by @​RainMeoCat in typicode/husky#1497

New Contributors

• @​RainMeoCat made their first contribution in typicode/husky#1497

Full Changelog: typicode/husky@v9.1.4...v9.1.5

Commits

• 2fee8d2 9.1.5
• 397e7f0 fixes #1494 support pre-merge-commit hook
• See full diff in compare view

Updates type-fest from 4.23.0 to 4.26.0

Release notes

Sourced from type-fest's releases.

v4.26.0

• Add UnionToTuple type (#945) 1f4f7a1

sindresorhus/type-fest@v4.25.0...v4.26.0

v4.25.0

• Add StringRepeat type (#938) a83e87e
• Add Arrayable type #270 (#935) 9aabcb9

sindresorhus/type-fest@v4.24.0...v4.25.0

v4.24.0

• Path: Add bracketNotation option (#926) 3b15a94

sindresorhus/type-fest@v4.23.0...v4.24.0

Commits

• 0fdc7d2 4.26.0
• 1f4f7a1 Add UnionToTuple type (#945)
• f120d8a Tagged: Improve documentation (#943)
• 986faba Get: Update Path generic parameter (#932)
• 2967fe6 4.25.0
• a83e87e Add StringRepeat type (#938)
• f19a002 OmitDeep: Improve example (#937)
• 9aabcb9 Add Arrayable type #270 (#935)
• 6ed388f 4.24.0
• 3b15a94 Path: Add bracketNotation option (#926)
• 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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud