Skip to content

chore(deps): update all non-major dependencies #84

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

Merged
merged 2 commits into from
Jul 27, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2025

This PR contains the following updates:

Package Change Age Confidence
@antfu/eslint-config 4.16.2 -> 4.19.0 age confidence
@babel/types (source) 7.28.1 -> 7.28.2 age confidence
@types/node (source) 22.16.3 -> 22.16.5 age confidence
@vue/compiler-core (source) 3.5.17 -> 3.5.18 age confidence
@vue/compiler-dom (source) 3.5.17 -> 3.5.18 age confidence
@vue/compiler-sfc (source) 3.5.17 -> 3.5.18 age confidence
esbuild 0.25.6 -> 0.25.8 age confidence
knip (source) 5.61.3 -> 5.62.0 age confidence
unbuild 3.5.0 -> 3.6.0 age confidence
vue-tsc (source) 3.0.1 -> 3.0.4 age confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v4.19.0

Compare Source

v4.18.0

Compare Source

   🚀 Features
    View changes on GitHub

v4.17.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
babel/babel (@​babel/types)

v7.28.2

Compare Source

🐛 Bug Fix
  • babel-types
  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
vuejs/core (@​vue/compiler-core)

v3.5.18

Compare Source

Bug Fixes
evanw/esbuild (esbuild)

v0.25.8

Compare Source

  • 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

Compare Source

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

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

    This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

  • Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

    This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

    Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

  • Fix a TypeScript parsing edge case (#​4241)

    This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

    x = a ? (b) : c => d;
    y = a ? (b) : c => d : e;

    The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

  • Inline small constant strings when minifying

    Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

    // Original code
    const foo = 'foo'
    console.log({ [foo]: true })
    
    // Old output (with --minify --bundle --format=esm)
    var o="foo";console.log({[o]:!0});
    
    // New output (with --minify --bundle --format=esm)
    console.log({foo:!0});

    Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

webpro-nl/knip (knip)

v5.62.0

Compare Source

unjs/unbuild (unbuild)

v3.6.0

Compare Source

compare changes

🚀 Enhancements
  • Support absoluteJitiPath for stub mode (#​542)
🩹 Fixes
  • types: Improve type safety (#​516)
📖 Documentation
  • Remove wrong jsdoc for dts type (#​540)
🏡 Chore
✅ Tests
  • Only include src for coverage report (#​525)
❤️ Contributors
vuejs/language-tools (vue-tsc)

v3.0.4

Compare Source

Features
  • feat(language-service): check casing when dropping component into template - Thanks to @​KazariEX!
  • feat(language-service): native completion experience for slot names (#​5552) - Thanks to @​KazariEX!
Bug Fixes
  • fix(language-core): avoid clearing global types path when local compiler options is present - Thanks to @​KazariEX!
  • fix(language-core): do not evaluate skipTemplateCodegen when exposing $slots - Thanks to @​KazariEX!
  • fix(language-service): correct kind and order of component completion items - Thanks to @​KazariEX!
  • fix(component-meta): filter events out of props (#​5547) - Thanks to @​Akryum!
Other Changes
  • refactor(language-core): allow configuring checkUnknownEvents and checkUnknownComponents in sfc (#​5537) - Thanks to @​KazariEX!
  • chore(language-service): add restart server hint to global types warning - Thanks to @​KazariEX!

v3.0.3

Compare Source

Bug Fixes
  • fix(language-core): find node_modules based on file's directory (#​5525) - Thanks to @​KazariEX!
  • fix(language-core): do not spread exposed object (#​5526) - Thanks to @​KazariEX!
  • fix(vscode): prompt manual reload in remote envs (#​5530)
Other Changes

v3.0.2

Compare Source


Configuration

📅 Schedule: Branch creation - "on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

pkg-pr-new bot commented Jul 21, 2025

Open in StackBlitz

npm i https://pkg.pr.new/vue-sfc-transformer@84

commit: aa5c66b

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 5e7f589 to a7e8e27 Compare July 24, 2025 07:10
@Teages Teages self-assigned this Jul 24, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a7e8e27 to 07bbdb0 Compare July 24, 2025 11:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 07bbdb0 to 5b596b2 Compare July 24, 2025 20:50
@Teages Teages merged commit 313d28d into main Jul 27, 2025
4 checks passed
@Teages Teages deleted the renovate/all-minor-patch branch July 27, 2025 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant