Skip to content

chore(deps): bump the npm_and_yarn group across 3 directories with 8 updates #2017

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

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 30, 2025

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps the npm_and_yarn group with 4 updates in the / directory: esbuild, nanoid, rollup and tar-fs.
Bumps the npm_and_yarn group with 5 updates in the /electron-test directory:

Package From To
esbuild 0.23.1 0.25.8
tsx 4.19.2 4.20.3
rollup 4.34.7 4.46.2
tar-fs 3.0.8 3.1.0
undici 6.21.1 6.21.3

Bumps the npm_and_yarn group with 4 updates in the /examples/vite-example directory: nanoid, rollup, vite and postcss.

Updates esbuild from 0.25.0 to 0.25.8

Release notes

Sourced from esbuild's releases.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
      #has = (a: string) => dict.has(a);
      has = window
        ? (word: string): boolean => this.#has(word)
        : this.#has;
    }
  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
    import source from from 'bar'
    import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
      const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
      const bar = await import.source("<specifier>");

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
      #has = (a: string) => dict.has(a);
      has = window
        ? (word: string): boolean => this.#has(word)
        : this.#has;
    }
  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
    import source from from 'bar'
    import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
      const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";

... (truncated)

Commits
  • 8c71947 publish 0.25.8 to npm
  • 0508f24 some parsing fixes for source phase imports
  • 6e4be2f js parser: recover from bad #private identifiers
  • c9c6357 fix #4248: #private ids in arrow fn body in ?:
  • 9b42f68 publish 0.25.7 to npm
  • 9ba01d1 abs-paths: js api and tests
  • ca196c9 fix for parser backtracking crash
  • 2979b84 fix #4241: ts arrow function type backtrack (hack)
  • 1180410 fix an unused variable warning
  • fc3da57 fix #4238: add defer and source import phases
  • Additional commits viewable in compare view

Updates nanoid from 3.3.8 to 3.3.11

Release notes

Sourced from nanoid's releases.

3.3.11

  • Fixed React Native support.

3.3.10

3.3.9

  • Reduced npm package size.
Changelog

Sourced from nanoid's changelog.

3.3.11

  • Fixed React Native support.

3.3.10

3.3.9

  • Reduced npm package size.
Commits

Updates rollup from 4.22.4 to 4.46.2

Release notes

Sourced from rollup's releases.

v4.46.2

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

v4.46.1

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

v4.46.0

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

v4.45.3

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

... (truncated)

Changelog

Sourced from rollup's changelog.

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

Pull Requests

  • #6014: chore(deps): update dependency @​vue/language-server to v3 (@​renovate[bot])

... (truncated)

Commits

Updates tar-fs from 3.0.9 to 3.1.0

Commits

Updates esbuild from 0.23.1 to 0.25.8

Release notes

Sourced from esbuild's releases.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
      #has = (a: string) => dict.has(a);
      has = window
        ? (word: string): boolean => this.#has(word)
        : this.#has;
    }
  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
    import source from from 'bar'
    import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
      const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";
      const bar = await import.source("<specifier>");

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

    class CachedDict {
      #has = (a: string) => dict.has(a);
      has = window
        ? (word: string): boolean => this.#has(word)
        : this.#has;
    }
  • Fix a regression with the parsing of source phase imports

    The change in the previous release to parse source phase imports failed to properly handle the following cases:

    import source from 'bar'
    import source from from 'bar'
    import source type foo from 'bar'

    Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

0.25.7

  • Parse and print JavaScript imports with an explicit phase (#4238)

    This release adds basic syntax support for the defer and source import phases in JavaScript:

    • defer

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

      import defer * as foo from "<specifier>";
      const bar = await import.defer("<specifier>");

      Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

    • source

      This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

      import source foo from "<specifier>";

... (truncated)

Commits
  • 8c71947 publish 0.25.8 to npm
  • 0508f24 some parsing fixes for source phase imports
  • 6e4be2f js parser: recover from bad #private identifiers
  • c9c6357 fix #4248: #private ids in arrow fn body in ?:
  • 9b42f68 publish 0.25.7 to npm
  • 9ba01d1 abs-paths: js api and tests
  • ca196c9 fix for parser backtracking crash
  • 2979b84 fix #4241: ts arrow function type backtrack (hack)
  • 1180410 fix an unused variable warning
  • fc3da57 fix #4238: add defer and source import phases
  • Additional commits viewable in compare view

Updates tsx from 4.19.2 to 4.20.3

Release notes

Sourced from tsx's releases.

v4.20.3

4.20.3 (2025-06-13)

Bug Fixes


This release is also available on:

v4.20.2

4.20.2 (2025-06-12)

Bug Fixes


This release is also available on:

v4.20.1

4.20.1 (2025-06-11)

Bug Fixes

  • json: handle keys with special characters (9bd2546)

This release is also available on:

v4.20.0

4.20.0 (2025-06-11)

Bug Fixes

... (truncated)

Commits
  • dadcf27 fix: revert v4.20 changes
  • 2d1aaee chore: upgrade manten
  • c188268 fix: support ambiguous package (#79)
  • 602f1b1 chore: debug to accept levels (#77)
  • 5172c47 test: log node-pty failure stdout
  • 1e8f17b refactor: node-pty test code
  • 9bd2546 fix(json): handle keys with special characters
  • e97fe67 test: failed pty tests logs
  • 532c50a tests: fix Windows tests
  • ec316d3 feat: support latest Node versions
  • Additional commits viewable in compare view

Updates rollup from 4.34.7 to 4.46.2

Release notes

Sourced from rollup's releases.

v4.46.2

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

v4.46.1

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

v4.46.0

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

v4.45.3

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

... (truncated)

Changelog

Sourced from rollup's changelog.

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

Pull Requests

  • #6014: chore(deps): update dependency @​vue/language-server to v3 (@​renovate[bot])

... (truncated)

Commits

Updates tar-fs from 3.0.8 to 3.1.0

Commits

Updates undici from 6.21.1 to 6.21.3

Release notes

Sourced from undici's releases.

v6.21.3

What's Changed

Full Changelog: nodejs/undici@v6.21.2...v6.21.3

v6.21.2

What's Changed

New Contributors

Full Changelog: nodejs/undici@v6.21.1...v6.21.2

Commits

Updates nanoid from 3.3.6 to 3.3.11

Release notes

Sourced from nanoid's releases.

3.3.11

  • Fixed React Native support.

3.3.10

3.3.9

  • Reduced npm package size.
Changelog

Sourced from nanoid's changelog.

3.3.11

  • Fixed React Native support.

3.3.10

3.3.9

  • Reduced npm package size.
Commits

Updates rollup from 3.29.4 to 3.29.5

Release notes

Sourced from rollup's releases.

v4.46.2

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

v4.46.1

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

v4.46.0

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

v4.45.3

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

... (truncated)

Changelog

Sourced from rollup's changelog.

4.46.2

2025-07-29

Bug Fixes

  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#6041)

Pull Requests

4.46.1

2025-07-28

Bug Fixes

  • Do not fail when using the in operator on external namespaces (#6036)

Pull Requests

  • #6036: disables optimization for external namespace when using the in operator (@​TrickyPi)

4.46.0

2025-07-27

Features

  • Optimize in checks on namespaces to keep them treeshake-able (#6029)

Pull Requests

4.45.3

2025-07-26

Bug Fixes

  • Do not fail build if a const is reassigned but warn instead (#6020)
  • Fail with a helpful error message if an exported binding is not defined (#6023)

Pull Requests

  • #6014: chore(deps): update dependency @​vue/language-server to v3 (@​renovate[bot])

... (truncated)

Commits

Updates vite from 4.5.3 to 4.5.14

Release notes

Sourced from vite's releases.

v4.5.14

Please refer to CHANGELOG.md for details.

v4.5.13

Please refer to CHANGELOG.md for details.

v4.5.12

Please refer to CHANGELOG.md for details.

v4.5.11

Please refer to CHANGELOG.md for details.

v4.5.10

Please refer to CHANGELOG.md for details.

v4.5.9

Please refer to CHANGELOG.md for details.

v4.5.8

Please refer to CHANGELOG.md for details.

v4.5.7

Please refer to CHANGELOG.md for details.

v4.5.6

This version contains a breaking change due to security fixes. See GHSA-vg6x-rcgg-rjx6 for more details.

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

4.5.14 (2025-04-30)

4.5.13 (2025-04-10)

4.5.12 (2025-04-03)

4.5.11 (2025-03-31)

4.5.10 (2025-03-24)

4.5.9 (2025-01-21)

4.5.8 (2025-01-20)

4.5.7 (2025-01-20)

  • fix: crypto.getRandomValues is not available in old Node versions (#19237) (f4d3c46), closes #19237

... (truncated)

Commits

…updates

Bumps the npm_and_yarn group with 4 updates in the / directory: [esbuild](https://github.com/evanw/esbuild), [nanoid](https://github.com/ai/nanoid), [rollup](https://github.com/rollup/rollup) and [tar-fs](https://github.com/mafintosh/tar-fs).
Bumps the npm_and_yarn group with 5 updates in the /electron-test directory:

| Package | From | To |
| --- | --- | --- |
| [esbuild](https://github.com/evanw/esbuild) | `0.23.1` | `0.25.8` |
| [tsx](https://github.com/privatenumber/tsx) | `4.19.2` | `4.20.3` |
| [rollup](https://github.com/rollup/rollup) | `4.34.7` | `4.46.2` |
| [tar-fs](https://github.com/mafintosh/tar-fs) | `3.0.8` | `3.1.0` |
| [undici](https://github.com/nodejs/undici) | `6.21.1` | `6.21.3` |

Bumps the npm_and_yarn group with 4 updates in the /examples/vite-example directory: [nanoid](https://github.com/ai/nanoid), [rollup](https://github.com/rollup/rollup), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) and [postcss](https://github.com/postcss/postcss).


Updates `esbuild` from 0.25.0 to 0.25.8
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.0...v0.25.8)

Updates `nanoid` from 3.3.8 to 3.3.11
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@3.3.8...3.3.11)

Updates `rollup` from 4.22.4 to 4.46.2
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.22.4...v4.46.2)

Updates `tar-fs` from 3.0.9 to 3.1.0
- [Commits](mafintosh/tar-fs@v3.0.9...v3.1.0)

Updates `esbuild` from 0.23.1 to 0.25.8
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.0...v0.25.8)

Updates `tsx` from 4.19.2 to 4.20.3
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.19.2...v4.20.3)

Updates `rollup` from 4.34.7 to 4.46.2
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.22.4...v4.46.2)

Updates `tar-fs` from 3.0.8 to 3.1.0
- [Commits](mafintosh/tar-fs@v3.0.9...v3.1.0)

Updates `undici` from 6.21.1 to 6.21.3
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v6.21.1...v6.21.3)

Updates `nanoid` from 3.3.6 to 3.3.11
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@3.3.8...3.3.11)

Updates `rollup` from 3.29.4 to 3.29.5
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.22.4...v4.46.2)

Updates `vite` from 4.5.3 to 4.5.14
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v4.5.14/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v4.5.14/packages/vite)

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

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.8
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: nanoid
  dependency-version: 3.3.11
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-version: 4.46.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tar-fs
  dependency-version: 3.1.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.8
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tsx
  dependency-version: 4.20.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-version: 4.46.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tar-fs
  dependency-version: 3.1.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 6.21.3
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: nanoid
  dependency-version: 3.3.11
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-version: 3.29.5
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: vite
  dependency-version: 4.5.14
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: postcss
  dependency-version: 8.5.6
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 30, 2025

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/npm_and_yarn-a58ac61cad branch July 30, 2025 16:10
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 javascript Pull requests that update javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant