GopherDrop icon indicating copy to clipboard operation
GopherDrop copied to clipboard
verified publisher icon kek-Sec

chore(deps): bump the npm_and_yarn group across 1 directory with 4 updates

Open dependabot[bot] opened this issue 9 months ago • 0 comments

Bumps the npm_and_yarn group with 4 updates in the /ui directory: vite, esbuild, vite-plugin-vuetify and @vitejs/plugin-vue.

Updates vite from 4.5.9 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.

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)

Commits

Updates esbuild from 0.18.20 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.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}

    // Old output (with esbuild v0.19.9)
    
class Foo extends Bar {
    
constructor() {
    
super();
    
this.#private = 1;
    
}
    
#private;
    
}
    

    // Old output (with esbuild v0.19.10)
    
class Foo extends Bar {
    
constructor() {
    
this.#private = 1;
    
super();
    
}
    
#private;
    
}
    

    // New output
    
class Foo extends Bar {
    
#private = 1;
    
constructor() {
    
super();
    
}
    
}

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (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 vite-plugin-vuetify from 1.0.1 to 2.1.1

Release notes

Sourced from vite-plugin-vuetify's releases.

v2.0.0

Changelogs for each package are now a separate file in their respective directories: https://github.com/vuetifyjs/vuetify-loader/tree/master/packages

v1.9.2

Bug Fixes

  • auto-import directives with v-on and v-bind (d0e115c), closes #258

v1.9.1

Bug Fixes

v1.9.0

Features

v1.7.3

Bug Fixes

  • add check before calling find on vue rule (#170) (22e2492)
  • add warning when used with asset modules (d5446df)
  • clone rules before adding oneOf (9a99f29), closes #186

v1.7.2

Bug Fixes

v1.7.1

Bug Fixes

v1.7.0

Features

v1.6.0

Bug Fixes

  • don't try to load custom blocks in .vue files (86751a1)
  • handle multiple vue-loader rules (9f0e669), closes #106

... (truncated)

Commits

Updates @vitejs/plugin-vue from 4.6.2 to 6.0.0

Release notes

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

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

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

6.0.0 (2025-06-24)

Bug Fixes

  • deps: update all non-major dependencies (#590) (43426c8)
  • deps: update all non-major dependencies (#600) (a4c32a8)
  • deps: update all non-major dependencies (#605) (67534e5)
  • deps: update all non-major dependencies (#609) (98c52eb)

Miscellaneous Chores

  • add description and keywords field to package.json (#604) (67ab76b)
  • deps: update dependency rollup to ^4.41.1 (#591) (256ac31)
  • deps: update dependency rollup to ^4.43.0 (#601) (a495edf)
  • remove Vite 7 beta from supported range (#598) (c7ddd62)

Code Refactoring

6.0.0-beta.2 (2025-06-06)

⚠ BREAKING CHANGES

  • bump required node version to 20.19+, 22.12+ and drop CJS build (#596)

Features

Bug Fixes

Code Refactoring

  • bump required node version to 20.19+, 22.12+ and drop CJS build (#596) (56df545)

6.0.0-beta.1 (2025-06-02)

Bug Fixes

6.0.0-beta.0 (2025-05-21)

⚠ BREAKING CHANGES

  • vue: separate include and exclude from api.options and add filter (#582)

Features

  • vue: separate include and exclude from api.options and add filter (#582) (e3beac8)

... (truncated)

Commits

Updates vite from 4.5.14 to 7.0.5

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.

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)

Commits

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 You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Jul 23 '25 12:07 dependabot[bot]