Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 15, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Change Age Confidence
@nuxt/content (source) ^3.6.3 -> ^3.7.1 age confidence
@nuxt/ui-pro (source) ^3.3.3 -> ^3.3.6 age confidence
eslint (source) ^9.35.0 -> ^9.37.0 age confidence
jiti ^2.5.1 -> ^2.6.1 age confidence
pnpm (source) 10.15.1 -> 10.18.0 age confidence
release-it ^19.0.4 -> ^19.0.5 age confidence
typescript (source) ^5.9.2 -> ^5.9.3 age confidence
vue (source) ^3.5.21 -> ^3.5.22 age confidence
vue-component-meta (source) ^3.0.6 -> ^3.1.0 age confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.7.1

Compare Source

Bug Fixes
  • remove zod and zod-to-json-schema from optional deps (#​3541) (8e038f0)

v3.7.0

Compare Source

Features
  • adopt standard schema spec and support different validators (#​3524) (46a1004)
  • inherit component prop types in content collection (#​3451) (a620a2c)
Bug Fixes
  • ProseCode preview syntax highlighting (#​3491) (4a725bd)
  • add dependency at Nuxt root dir (#​3525) (71f2989)
  • block experimental sqlite warning on node (5ac31da)
  • deprecate nitro export in favor of server (ec97064)
  • do not register close hook if websocket is disabled (#​3474) (9edcc8f)
  • ignore .DS_Store files in all subdirectories (c7a9af3)
  • ignore OSX meta file .DS_Store (fe5d7f9)
  • improve websocket and watcher cleanup handling (#​3478) (8041807)
  • inherit: cache component meta (e9658de)
  • inherit: issue with property definition in arrays (873b768)
  • inherit: try resolve component from root directory (b0073f1)
  • inherit: type generation (63500f3)
  • normalize source cwd (#​3532) (0a34742)
  • nuxthub: missing line separator in database migrations (#​3464) (4983443)
  • use listhen's publicUrl if available (#​3500) (fb0f022)
nuxt/ui-pro (@​nuxt/ui-pro)

v3.3.6

Compare Source

v3.3.5

Compare Source

v3.3.4

Compare Source

eslint/eslint (eslint)

v9.37.0

Compare Source

v9.36.0

Compare Source

unjs/jiti (jiti)

v2.6.1

Compare Source

compare changes

🩹 Fixes
  • interop: Only passthrough default if it is not a promise (#​408)
📦 Build
  • Revert to terser-webpack-plugin (#​407)
🏡 Chore
❤️ Contributors

v2.6.0

Compare Source

compare changes

🔥 Performance
  • Lazy load babel transform (#​405)
🩹 Fixes
  • cjs-interop: Handle function default exports (#​396)
  • Always use native for node: specifiers (#​392)
📦 Build
🏡 Chore
✅ Tests
  • Update deno and bun native test ignores (df844f8)
  • New bench script (6404427)
❤️ Contributors
  • Pooya Parsa (@​pi0)
  • Volodymyr Kolesnykov (@​sjinks)
  • Jungwoo LEE <jungwoo3490@​naver.com>
pnpm/pnpm (pnpm)

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:
      - "@&#8203;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.
release-it/release-it (release-it)

v19.0.5

Compare Source

microsoft/TypeScript (typescript)

v5.9.3

Compare Source

vuejs/core (vue)

v3.5.22

Compare Source

Bug Fixes
Features
  • custom-element: allow specifying additional options for shadowRoot in custom elements (#​12965) (47e628d), closes #​12964
Reverts
  • Revert "fix(hmr): prevent VUE_HMR_RUNTIME from being overwritten by vue runtime in 3rd-party libraries" (#​13925) (6b68f72), closes #​13925
vuejs/language-tools (vue-component-meta)

v3.1.0

Compare Source

Performance
Other Changes

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!

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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ae2baf3 to c432806 Compare September 16, 2025 03:30
Copy link

pkg-pr-new bot commented Sep 16, 2025

npm i https://pkg.pr.new/nuxt-component-meta@91

commit: c02d401

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 245e68c to 34912d1 Compare September 23, 2025 17:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 5503a47 to 6ec9c68 Compare October 1, 2025 21:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 3077af8 to 6b6224b Compare October 3, 2025 16:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6b6224b to c02d401 Compare October 3, 2025 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants