Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump the dev-dependencies group across 1 directory with 10 updates #1052

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 23, 2024

Bumps the dev-dependencies group with 10 updates in the / directory:

Package From To
@biomejs/biome 1.8.3 1.9.4
cypress 13.13.2 13.15.0
esbuild 0.23.0 0.24.0
stylelint 16.8.1 16.10.0
tsx 4.16.5 4.19.1
typescript 5.5.4 5.6.3
@types/react 18.3.3 18.3.12
@types/react-dom 18.3.0 18.3.1
@vitejs/plugin-react 4.3.1 4.3.3
vite 5.4.0 5.4.10

Updates @biomejs/biome from 1.8.3 to 1.9.4

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.9.4

Analyzer

Bug fixes

  • Improved the message for unused suppression comments. Contributed by @​dyc3

  • Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole incorrectly reports a role for non-interactive elements. Contributed by @​eryue0220

  • noSuspiciousSemicolonInJsx now catches suspicious semicolons in React fragments. Contributed by @​vasucp1207

CLI

Enhancements

  • The --summary reporter now reports parsing diagnostics too. Contributed by @​ematipico

  • Improved performance of GritQL queries by roughly 25-30%. Contributed by @​arendjr

Configuration

Bug fixes

  • Fix an issue where the JSON schema marked lint rules options as mandatory. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix #4121. Respect line width when printing multiline strings. Contributed by @​ah-yu

Linter

New features

Bug Fixes

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.9.4 (2024-10-17)

Analyzer

Bug fixes

  • Implement GraphQL suppression action. Contributed by @​vohoanglong0107

  • Improved the message for unused suppression comments. Contributed by @​dyc3

  • Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole incorrectly reports a role for non-interactive elements. Contributed by @​eryue0220

  • noSuspiciousSemicolonInJsx now catches suspicious semicolons in React fragments. Contributed by @​vasucp1207

  • The syntax rule noTypeOnlyImportAttributes now ignores .cts files (#4361).

    Since TypeScript 5.3, type-only imports can be associated to an import attribute in CommonJS-enabled files. See the TypeScript docs.

    The following code is no longer reported as a syntax error:

    import type { TypeFromRequire } from "pkg" with {
        "resolution-mode": "require"
    };

    Note that this is only allowed in files ending with the cts extension.

    Contributed by @​Conaclos

CLI

Enhancements

  • The --summary reporter now reports parsing diagnostics too. Contributed by @​ematipico

  • Improved performance of GritQL queries by roughly 25-30%. Contributed by @​arendjr

Configuration

Bug fixes

  • Fix an issue where the JSON schema marked lint rules options as mandatory. Contributed by @​ematipico

Editors

Formatter

Bug fixes

... (truncated)

Commits

Updates cypress from 13.13.2 to 13.15.0

Release notes

Sourced from cypress's releases.

v13.15.0

Changelog: https://docs.cypress.io/guides/references/changelog#13-15-0

v13.14.2

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

v13.14.1

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

v13.14.0

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

v13.13.3

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

Commits
  • 5afb929 chore: Update Chrome (stable) to 129.0.6668.70 (#30279)
  • 0d2248c chore: release 13.15.0 (#30292)
  • 8d71cc4 chore: Update changelog to 'addresses' rather than addressed in (#30275)
  • 1d84532 feat: Improve UX when Test Replay upload fails due to slow upload (#30235)
  • fbe51fc chore: fix net_stubbing flake (#30276)
  • 88900e7 chore: update tests to skip the welcome screen on launchpad tests. (#30240)
  • 954cc50 chore: [Snyk] Security upgrade express from 4.19.2 to 4.21.0 in packages/grap...
  • 3ff88b7 chore: Fix double bugfixes headings in changelog (#30268)
  • 0bdf495 chore: Update Chrome (beta) to 130.0.6723.6 (#30256)
  • f7946de docs: update guides/building-release-artifacts.md (#30257)
  • Additional commits viewable in compare view

Updates esbuild from 0.23.0 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

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";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

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

... (truncated)

Commits

Updates stylelint from 16.8.1 to 16.10.0

Release notes

Sourced from stylelint's releases.

16.10.0

  • Changed: shorthand-property-no-redundant-values reported ranges (#8008) (@​Mouvedia).
  • Added: formatter configuration property (#7826) (@​emmacharp).
  • Added: validate option to Node.js API and --validate CLI flag (#8009) (@​Mouvedia).
  • Added: fixed section to the output of the verbose formatter (#7985) (@​Mouvedia).
  • Added: support for string | RegExp to ignoreValues option of value-no-vendor-prefix (#7969) (@​Mouvedia).
  • Added: support for string to ignoreLonghands option of declaration-block-no-redundant-longhand-properties (#7971) (@​Mouvedia).
  • Fixed: at-rule-no-unknown false positives for @position-try (#7968) (@​yelizsevinc).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for grid-column/grid-row (#8023) (@​ryo-manba).
  • Fixed: declaration-property-value-no-unknown false negatives/positives via [email protected] (#7993) (@​Mouvedia).
  • Fixed: declaration-property-value-no-unknown reported ranges and message (#8003) (@​romainmenke).
  • Fixed: keyframe-selector-notation reported ranges (#7992) (@​romainmenke).
  • Fixed: length-zero-no-unit false positives for Sass variables (#8035) (@​ryo-manba).
  • Fixed: no-descending-specificity reported ranges (#7996) (@​romainmenke).
  • Fixed: selector-anb-no-unmatchable reported ranges and message (#8001) (@​romainmenke).
  • Fixed: string formatter handling of log symbols for non-Unicode terminals (#7981) (@​Mouvedia).
  • Fixed: built .cjs files to address Rollup vulnerability (#8010) (@​ybiquitous).
  • Fixed: incorrect config option for Node.js API with extends and overrides (#8030) (@​ybiquitous).
  • Fixed: stricter validation for the options of declaration-property-max-values, declaration-property-value-no-unknown and number-max-precision (#7975) (@​Mouvedia).

16.9.0

  • Changed: secondaryOptions argument type of the Rule function (#7950) (@​Mouvedia).
  • Fixed: color-function-notation reporting functions with less than 3 arguments (#7948) (@​Mouvedia).
  • Fixed: declaration-property-value-no-unknown false positives/negatives (#7944 & #7957 & #7956) (@​Mouvedia & @​sidverma32).
    • false positives: overflow, word-break, width
    • false negatives: anchor-name, field-sizing, text-box-edge, text-box-trim, text-spacing-trim, text-wrap, text-wrap-mode, text-wrap-style, view-timeline, view-timeline-axis, view-timeline-inset, view-timeline-name, view-transition-name
  • Fixed: keyframe-block-no-duplicate-selectors/keyframe-declaration-no-important/keyframe-selector-notation/no-unknown-animations false negatives for @-o-keyframes and @-ms-keyframes (#7953) (@​Mouvedia).
  • Fixed: no-duplicate-selectors reported ranges (#7938) (@​romainmenke).
  • Fixed: property-no-vendor-prefix report for -webkit-background-size (#7940) (@​Mouvedia).
  • Fixed: selector-class-pattern reported ranges (#7959) (@​Mouvedia).
  • Fixed: selector-no-qualifying-type reported ranges (#7937) (@​romainmenke).
  • Fixed: honour Node.js --no-deprecation flag for rule deprecation warnings (#7943) (@​Mouvedia).

16.8.2

Changelog

Sourced from stylelint's changelog.

16.10.0

  • Changed: shorthand-property-no-redundant-values reported ranges (#8008) (@​Mouvedia).
  • Added: formatter configuration property (#7826) (@​emmacharp).
  • Added: validate option to Node.js API and --validate CLI flag (#8009) (@​Mouvedia).
  • Added: fixed section to the output of the verbose formatter (#7985) (@​Mouvedia).
  • Added: support for string | RegExp to ignoreValues option of value-no-vendor-prefix (#7969) (@​Mouvedia).
  • Added: support for string to ignoreLonghands option of declaration-block-no-redundant-longhand-properties (#7971) (@​Mouvedia).
  • Fixed: at-rule-no-unknown false positives for @position-try (#7968) (@​yelizsevinc).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for grid-column/grid-row (#8023) (@​ryo-manba).
  • Fixed: declaration-property-value-no-unknown false negatives/positives via [email protected] (#7993) (@​Mouvedia).
  • Fixed: declaration-property-value-no-unknown reported ranges and message (#8003) (@​romainmenke).
  • Fixed: keyframe-selector-notation reported ranges (#7992) (@​romainmenke).
  • Fixed: length-zero-no-unit false positives for Sass variables (#8035) (@​ryo-manba).
  • Fixed: no-descending-specificity reported ranges (#7996) (@​romainmenke).
  • Fixed: selector-anb-no-unmatchable reported ranges and message (#8001) (@​romainmenke).
  • Fixed: string formatter handling of log symbols for non-Unicode terminals (#7981) (@​Mouvedia).
  • Fixed: built .cjs files to address Rollup vulnerability (#8010) (@​ybiquitous).
  • Fixed: incorrect config option for Node.js API with extends and overrides (#8030) (@​ybiquitous).
  • Fixed: stricter validation for the options of declaration-property-max-values, declaration-property-value-no-unknown and number-max-precision (#7975) (@​Mouvedia).

16.9.0

  • Changed: secondaryOptions argument type of the Rule function (#7950) (@​Mouvedia).
  • Fixed: color-function-notation reporting functions with less than 3 arguments (#7948) (@​Mouvedia).
  • Fixed: declaration-property-value-no-unknown false positives/negatives (#7944 & #7957 & #7956) (@​Mouvedia & @​sidverma32).
    • false positives: overflow, word-break, width
    • false negatives: anchor-name, field-sizing, text-box-edge, text-box-trim, text-spacing-trim, text-wrap, text-wrap-mode, text-wrap-style, view-timeline, view-timeline-axis, view-timeline-inset, view-timeline-name, view-transition-name
  • Fixed: keyframe-block-no-duplicate-selectors/keyframe-declaration-no-important/keyframe-selector-notation/no-unknown-animations false negatives for @-o-keyframes and @-ms-keyframes (#7953) (@​Mouvedia).
  • Fixed: no-duplicate-selectors reported ranges (#7938) (@​romainmenke).
  • Fixed: property-no-vendor-prefix report for -webkit-background-size (#7940) (@​Mouvedia).
  • Fixed: selector-class-pattern reported ranges (#7959) (@​Mouvedia).
  • Fixed: selector-no-qualifying-type reported ranges (#7937) (@​romainmenke).
  • Fixed: honour Node.js --no-deprecation flag for rule deprecation warnings (#7943) (@​Mouvedia).

16.8.2

Commits
  • c360343 16.10.0
  • a8bb7ab Prepare 16.10.0 (#7970)
  • 8eb19d0 Document issue types for maintainers (#8036)
  • f5e83b1 Fix length-zero-no-unit false positives for Sass variables (#8035)
  • 99030ac Fix declaration-block-no-redundant-longhand-properties autofix for `grid-co...
  • 3fca687 Bump typescript from 5.6.2 to 5.6.3 in the typescript group (#8031)
  • 530f0ee Bump css-functions-list from 3.2.2 to 3.2.3 (#8033)
  • edaa508 Bump rollup from 4.22.5 to 4.24.0 (#8032)
  • ab2141e Fix incorrect config option for Node.js API with extends and overrides ...
  • baf7c0e Bump postcss-safe-parser from 7.0.0 to 7.0.1 in the postcss group (#8021)
  • Additional commits viewable in compare view

Updates tsx from 4.16.5 to 4.19.1

Release notes

Sourced from tsx's releases.

v4.19.1

4.19.1 (2024-09-12)

Bug Fixes


This release is also available on:

v4.19.0

4.19.0 (2024-08-27)

Features

  • watch: deprecate ignore flag in favor or exclude flag (157c3ec)

This release is also available on:

v4.18.0

4.18.0 (2024-08-24)

Features

  • watch: --include CLI flag to watch additional files (#625) (474ea71)

This release is also available on:

v4.17.1

4.17.1 (2024-08-24)

... (truncated)

Commits
  • 0329bfc fix(cjs): patch module.path for accurate cache ID
  • 44ed37f fix(cjs): resolve ts extensions from js when namespaced
  • ac77527 test: outdent api fixtures
  • 157c3ec feat(watch): deprecate ignore flag in favor or exclude flag
  • 474ea71 feat(watch): --include CLI flag to watch additional files (#625)
  • af370e7 fix(esm): package entry TS resolution for Node 20.17 & 22.6
  • 1b80d5d docs: add premium sponsors
  • 6c8eae0 chore: upgrade lintroll
  • bd83d3b feat: upgrade esbuild to 0.23 (#615)
  • See full diff in compare view

Updates typescript from 5.5.4 to 5.6.3

Release notes

Sourced from typescript's releases.

TypeScript 5.6.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.6 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.6 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

... (truncated)

Commits
  • d48a5cf Bump version to 5.6.3 and LKG
  • fefa70a 🤖 Pick PR #60083 (Don't issue implicit any when obtai...) into release-5.6 (#...
  • ff71692 [release-5.6] Remove tsbuildInfo specification error now that we need it for ...
  • 1f44dcf 🤖 Pick PR #60157 (fix automatic type acquisition) into release-5.6 (#60169)
  • a7e3374 Bump version to 5.6.2 and LKG
  • 2063357 🤖 Pick PR #59708 (LEGO: Pull request from lego/hb_537...) into release-5.6 (#...
  • 4fe7e41 🤖 Pick PR #59670 (fix(59649): ts Move to a new file d...) into release-5.6 (#...
  • 1a03e53 🤖 Pick PR #59761 (this can be nullish) into release-5.6 (#59762)
  • 6212132 Update LKG
  • bbb5faf 🤖 Pick PR #59542 (Fixing delay caused in vscode due t...) into release-5.6 (#...
  • Additional commits viewable in compare view

Updates @types/react from 18.3.3 to 18.3.12

Commits

Updates @types/react-dom from 18.3.0 to 18.3.1

Commits

Updates @vitejs/plugin-react from 4.3.1 to 4.3.3

Release notes

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

v4.3.3

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development
export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

v4.3.2

Ignore directive sourcemap error #369

Changelog

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

4.3.3 (2024-10-19)

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development
export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPl...
Description has been truncated

…ith 10 updates

Bumps the dev-dependencies group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `1.8.3` | `1.9.4` |
| [cypress](https://github.com/cypress-io/cypress) | `13.13.2` | `13.15.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.23.0` | `0.24.0` |
| [stylelint](https://github.com/stylelint/stylelint) | `16.8.1` | `16.10.0` |
| [tsx](https://github.com/privatenumber/tsx) | `4.16.5` | `4.19.1` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.5.4` | `5.6.3` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `18.3.3` | `18.3.12` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `18.3.0` | `18.3.1` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.3.1` | `4.3.3` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.0` | `5.4.10` |



Updates `@biomejs/biome` from 1.8.3 to 1.9.4
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/cli/v1.9.4/packages/@biomejs/biome)

Updates `cypress` from 13.13.2 to 13.15.0
- [Release notes](https://github.com/cypress-io/cypress/releases)
- [Changelog](https://github.com/cypress-io/cypress/blob/develop/CHANGELOG.md)
- [Commits](cypress-io/cypress@v13.13.2...v13.15.0)

Updates `esbuild` from 0.23.0 to 0.24.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.23.0...v0.24.0)

Updates `stylelint` from 16.8.1 to 16.10.0
- [Release notes](https://github.com/stylelint/stylelint/releases)
- [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint@16.8.1...16.10.0)

Updates `tsx` from 4.16.5 to 4.19.1
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.16.5...v4.19.1)

Updates `typescript` from 5.5.4 to 5.6.3
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.5.4...v5.6.3)

Updates `@types/react` from 18.3.3 to 18.3.12
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `@types/react-dom` from 18.3.0 to 18.3.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `@vitejs/plugin-react` from 4.3.1 to 4.3.3
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/v4.3.3/packages/plugin-react)

Updates `vite` from 5.4.0 to 5.4.10
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.10/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.10/packages/vite)

---
updated-dependencies:
- dependency-name: "@biomejs/biome"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: cypress
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: stylelint
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: tsx
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@types/react"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@types/react-dom"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@vitejs/plugin-react"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: vite
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 23, 2024
@dependabot dependabot bot requested a review from rikteg as a code owner October 23, 2024 23:51
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 24, 2024

Superseded by #1053.

@dependabot dependabot bot closed this Oct 24, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/dev-dependencies-80c1df1ea5 branch October 24, 2024 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants