Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 8, 2025

This PR contains the following updates:

Package Change Age Confidence
@vue/language-server (source) 3.0.6 -> 3.1.1 age confidence
pnpm (source) 10.15.0 -> 10.18.3 age confidence
sass 1.90.0 -> 1.93.2 age confidence
typescript (source) 5.9.2 -> 5.9.3 age confidence
vite (source) 7.1.4 -> 7.1.17 age confidence
vue-tsc (source) 3.0.6 -> 3.1.1 age confidence

Release Notes

vuejs/language-tools (@​vue/language-server)

v3.1.1

Compare Source

Features
  • feat(language-server): support --tsdk command line arg (#​5691)
Bug Fixes
  • fix(language-core): tolerate non-literal export default (#​5675) - Thanks to @​KazariEX!
  • fix(language-core): use component instance props as fallthrough attributes (#​5686) - Thanks to @​KazariEX!
  • fix(typescript-plugin): determine if variable is Ref by RefSymbol property (#​5687) - Thanks to @​KazariEX!
  • fix(language-core): exclude effect of comments on root node (#​5689) - Thanks to @​KazariEX!
  • fix(typescript-plugin): place __vue__ in project instead of program (#​5690)
  • fix(component-type-helpers): remove deprecated $scopedSlots support for Vue 2
  • fix(language-core): replace markdown links after sfc blocks processing (#​5695) - Thanks to @​KazariEX!
  • fix(language-core): do not report unused error on __VLS_export (#​5696) - Thanks to @​KazariEX!
Other Changes
  • refactor(language-core): reimplement writeGlobalTypes without side effects

v3.1.0

Compare Source

Performance
Other Changes

v3.0.9

Compare Source

Features
  • feat(language-server): support --tsdk command line arg (#​5691)

v3.0.8

Compare Source

Features
  • feat(vscode): introduce vue.server.path setting (#​5647)
Bug Fixes
  • fix(language-core): initialize properties of VueVirtualCode in constructor (#​5635) - Thanks to @​KazariEX!
  • fix(vscode): flatten reactivity visualization decorators (#​5642) - Thanks to @​KazariEX!
  • fix(vscode): normalize reactivity visualization ranges
  • fix(vscode): patch typescriptServerPlugin languages without FS hack
  • fix(language-service): do not provide semantic tokens and document highlights for non-file scheme files (#​5653) - Thanks to @​KazariEX!
Performance
  • perf(typescript-plugin): redo single-file language service for reactivity visualization (#​5652)
Other Changes
  • refactor(typescript-plugin): externalize reactivity analysis logic (#​5645) - Thanks to @​KazariEX!

v3.0.7

Compare Source

Bug Fixes
  • fix(vscode): show welcome page only when opening a Vue file
  • fix(language-core): generate slot parameters in the same way as interpolation (#​5618) - Thanks to @​KazariEX!
  • fix(language-core): do not generate variables for builtin directives - Thanks to @​KazariEX!
Other Changes
  • docs(vscode): add descriptions for premium feature configurations (#​5612) - Thanks to @​KazariEX!
  • refactor(typescript-plugin): explicitly request parameters (#​5623)
  • chore(lint): enable @typescript-eslint/no-unnecessary-condition (#​5630)
  • refactor(language-server): reimplement Reactivity Visualization in typescript plugin (#​5632)
  • refactor(language-server): parsing interpolations in extension client (#​5633)
  • refactor(vscode): reimplement Focus Mode base on folding ranges (#​5634)
  • chore(vscode): disable Focus Mode by default (#​5578)
  • refactor(vscode): set delay of reactivity visualization updates to 250ms - Thanks to @​KazariEX!
pnpm/pnpm (pnpm)

v10.18.3

Compare Source

Patch Changes
  • Fix a bug where pnpm would infinitely recurse when using verifyDepsBeforeInstall: install and pre/post install scripts that called other pnpm scripts #​10060.
  • Fixed scoped registry keys (e.g., @scope:registry) being parsed as property paths in pnpm config get when --location=project is used #​9362.
  • Remove pnpm-specific CLI options before passing to npm publish to prevent "Unknown cli config" warnings #​9646.
  • Fixed EISDIR error when bin field points to a directory #​9441.
  • Preserve version and hasBin for variations packages #​10022.
  • Fixed pnpm config set --location=project incorrectly handling keys with slashes (auth tokens, registry settings) #​9884.
  • When both pnpm-workspace.yaml and .npmrc exist, pnpm config set --location=project now writes to pnpm-workspace.yaml (matching read priority) #​10072.
  • Prevent a table width error in pnpm outdated --long #​10040.
  • Sync bin links after injected dependencies are updated by build scripts. This ensures that binaries created during build processes are properly linked and accessible to consuming projects #​10057.

v10.18.2

Compare Source

Patch Changes
  • pnpm outdated --long should work #​10040.
  • Replace ndjson with split2. Reduce the bundle size of pnpm CLI #​10054.
  • pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #​9963.
  • pnpm version switching should work when the pnpm home directory is in a symlinked directory #​9715.
  • Fix EPIPE errors when piping output to other commands #​10027.

v10.18.1

Compare Source

Patch Changes
  • Don't print a warning, when --lockfile-only is used #​8320.
  • pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #​5700.
  • When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes
  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes
  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
    minimumReleaseAgeExclude:
      - "@​eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes
  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
      - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist
    

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
    ├─┬ handlebars 4.7.7
    │ └── minimist 1.2.8
    └─┬ mv 2.1.1
      └─┬ mkdirp 0.5.6
        └── minimist 1.2.8
    

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
      finders: {
        react17: (ctx) => {
          return ctx.readManifest().peerDependencies?.react === "^17.0.0";
        },
      },
    };

    Now we can use this finder function by running:

    pnpm why --find-by=react17
    

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    └── graphql-tag 2.12.6
    

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
      finders: {
        react17: (ctx) => {
          const manifest = ctx.readManifest();
          if (manifest.peerDependencies?.react === "^17.0.0") {
            return `license: ${manifest.license}`;
          }
          return false;
        },
      },
    };

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    │   license: MIT
    └── graphql-tag 2.12.6
        license: MIT
    
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.
sass/dart-sass (sass)

v1.93.2

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix another error in the release process for @sass/types.

v1.93.1

Compare Source

  • No user-visible changes.
JavaScript API
  • Fix an error in the release process for @sass/types.

v1.93.0

Compare Source

  • Fix a crash when a style rule contains a nested @import, and the loaded file
    @uses a user-defined module as well as @includes a top-level mixin which
    emits top-level declarations.
JavaScript API
  • Release a @sass/types package which contains the type annotations used by
    both the sass and sass-embedded package without any additional code or
    dependencies.

v1.92.1

Compare Source

  • Fix a bug where variable definitions from one imported, forwarded module
    would not be passed as implicit configuration to a later imported, forwarded
    module.

v1.92.0

Compare Source

  • Breaking change: Emit declarations, childless at-rules, and comments in
    the order they appear in the source even when they're interleaved with nested
    rules. This obsoletes the mixed-decls deprecation.

  • Breaking change: The function name type() is now fully reserved for the
    plain CSS function. This means that @function definitions with the name
    type will produce errors, while function calls will be parsed as special
    function strings.

  • Configuring private variables using @use ... with, @forward ... with, and
    meta.load-css(..., $with: ...) is now deprecated. Private variables were
    always intended to be fully encapsulated within the module that defines them,
    and this helps enforce that encapsulation.

  • Fix a bug where @extend rules loaded through a mixture of @import and
    @use rules could fail to apply correctly.

Command-Line Interface
  • In --watch mode, delete the source map when the associated source file is
    deleted.

v1.91.0

Compare Source

  • Potentially breaking change: meta.inspect() (as well as other systems
    that use it such as @debug and certain error messages) now emits numbers
    with as high precision as is available instead of rounding to the nearest
    1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
    meta.inspect(), which is to provide full information about the structure of
    a Sass value.

  • Passing a rest argument ($arg...) before a positional or named argument when
    calling a function or mixin is now deprecated. This was always outside the
    specified syntax, but it was historically treated the same as passing the rest
    argument at the end of the argument list whether or not that matched the
    visual order of the arguments.

microsoft/TypeScript (typescript)

v5.9.3

Compare Source

vitejs/rolldown-vite (vite)

v7.1.17

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores

v7.1.16

Compare Source

Features
Bug Fixes
Reverts

v7.1.15

Compare Source

Bug Fixes
Miscellaneous Chores

v7.1.14

Compare Source

Features
Bug Fixes
  • use readFileSync to avoid "too many open files" (7c7ffdc)
Performance Improvements
  • use single regex for isEntirelyImport (ac1ceaf)
Documentation
Miscellaneous Chores

v7.1.13

Compare Source

Features
  • hmr: skip self-imports for import.meta.hot.invalidate (ebd134f)
  • update rolldown (007e115)

v7.1.12

Compare Source

Features
Bug Fixes
  • build: fix ssr environment emitAssets: true when sharedConfigBuild: true (#​20787) (4c4583c)
  • client: use CSP nonce when rendering error overlay (#​20791) (9bc9d12)
  • deps: update all non-major dependencies (#​20811) (9f2247c)
  • glob: handle glob imports from folders starting with dot (#​20800) (105abe8)
  • hmr: trigger prune event when import is removed from non hmr module (#​20768) (9f32b1d)
  • hmr: wait for import.meta.hot.prune callbacks to complete before running other HMRs (#​20698) (98a3484)

v7.1.11

Compare Source

Bug Fixes
  • deps: update all non-major dependencies (#​20773) (88af2ae)
  • esbuild: inject esbuild helper functions with minified $ variables correctly (#​20761) (7e8e004)
  • fallback terser to main thread when nameCache is provided (#​20750) (a679a64)
  • optimizer: avoid mutating optimizeDeps.rollupOptions.transforms for stable optimizer hash (#​417) (efed40f)
  • types: strict env typings fail when skipLibCheck is false (#​20755) (cc54e29)
Miscellaneous Chores

v7.1.10

Compare Source

Features

v7.1.9

Compare Source

Features
Bug Fixes
  • enable minify other than codegen for ES lib mode (ad72fc3)
Miscellaneous Chores

v7.1.8

Compare Source

Features
Miscellaneous Chores

v7.1.7

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.1.6

Compare Source

Features
Bug Fixes
  • build.minify: 'esbuild' + native plugins were not working (#​397) (1a05fc4)
  • oxc: respect oxc.typescript.onlyRemoveTypeImports if it's set (#​394) (dd64f89)

v7.1.5

Compare Source

Features
Bug Fixes
  • native-plugin: generate a more readable manifest (#​388) (e76ad17)

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Sep 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 009ce6c to d4dad7a Compare September 14, 2025 00:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from abeaafc to b92c915 Compare September 22, 2025 04:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 036d5b1 to 6abc3c9 Compare September 28, 2025 18:03
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 5d3ec25 to 4aef535 Compare October 7, 2025 04:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f018cef to 8154018 Compare October 14, 2025 10:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8154018 to 9ed8586 Compare October 14, 2025 18:00
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

Development

Successfully merging this pull request may close these issues.

0 participants