Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

chore(deps): update all non-major dependencies#476
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Mar 30, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@iconify-json/lucide ^1.2.121^1.2.126 age confidence devDependencies patch 1.2.127
@nuxt/devtools (source) ^3.4.1^3.4.2 age confidence devDependencies patch
@nuxt/eslint-config (source) ^1.16.0^1.17.0 age confidence devDependencies minor
@nuxt/module-builder 1.0.21.0.3 age confidence devDependencies patch
@nuxt/test-utils ^4.1.0^4.2.0 age confidence devDependencies minor
@nuxt/ui (source) ^4.10.0^4.11.0 age confidence devDependencies minor
@shikijs/core (source) ^4.4.2^4.4.3 age confidence dependencies patch
@shikijs/engine-javascript (source) ^4.4.2^4.4.3 age confidence dependencies patch
@shikijs/langs (source) ^4.4.2^4.4.3 age confidence dependencies patch
@shikijs/themes (source) ^4.4.2^4.4.3 age confidence dependencies patch
@shikijs/transformers (source) ^4.4.2^4.4.3 age confidence dependencies patch
@types/node (source) ^26.1.2^26.4.0 age confidence devDependencies minor
@vue/compiler-core (source) ^3.5.41^3.5.42 age confidence dependencies patch
eslint (source) ^10.8.0^10.9.1 age confidence devDependencies minor
mkdist 2.3.02.4.1 age confidence resolutions minor
node 2424.20.0 age confidence uses-with minor
pnpm (source) 11.20.011.24.0 age confidence packageManager minor
release-it ^20.2.0^20.2.1 age confidence devDependencies patch
shiki (source) ^4.4.2^4.4.3 age confidence dependencies patch
unwasm ^0.5.3^0.6.0 age confidence dependencies minor
vitest (source) ^4.1.10^4.1.11 age confidence devDependencies patch
vue-tsc (source) ^3.3.9^3.3.11 age confidence devDependencies patch

Release Notes

nuxt/devtools (@​nuxt/devtools)

v3.4.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
nuxt/eslint (@​nuxt/eslint-config)

v1.17.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
nuxt/module-builder (@​nuxt/module-builder)

v1.0.3

Compare Source

v1.0.3 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • update command defaults and descriptions (#​677)
📦 Build
🏡 Chore
  • migrate to pnpm v11 (#​738)
  • remove shamefully-hoist (#​580)
  • migrate resolutions/pnpm.overrides to pnpm-workspace.yaml (cfb45fb)
  • migrate npm badges and links to npmx.dev (afcf2fa)
  • revert pnpm trust policy and restore provenance action (aeb1d38)
  • update pnpm to 10.21 and enable trust policy (92eb2af)
✅ Tests
  • accept nuxt/app specifier for NuxtError in snapshot (809c89f)
  • update v4.5 error type as well (9412c91)
  • accept either #app or nuxt/app in generated declarations (#​727)
🤖 CI
  • use uppt release workflow (604d5b3)
  • add agent-scan workflow to flag bot-authored PRs (4442a14)
  • rename workflow (f7be1a6)
  • avoid checkout in reproduction (57e7ce9)
  • pin github actions to full-length commit shas (c3c8e72)
  • add provenance action to check for downgrades in provenance (d87d217)
  • run tests on node 20 (54c5f13)
🎉 New Contributors
❤️ Contributors
nuxt/test-utils (@​nuxt/test-utils)

v4.2.0

Compare Source

v4.2.0 is the next minor release.

👉 Changelog

compare changes

🚀 Enhancements
  • browser: add render helper for vitest browser mode (#​1725)
  • runtime-utils: add spy option to mount + render helpers (#​1762)
🩹 Fixes
  • runtime-utils: mockNuxtImport sourcemap mapped position (#​1787)
  • config: tolerate non-cloneable values when cloning config (#​1771)
  • e2e: honour setupTimeout in playwright + surface server logs (#​1785)
  • e2e: add explanation if server exited before being ready (#​1761)
  • module: handle string presets in auto-imports (#​1784)
  • config: don't run includeSource in both projects in defineVitestConfig (#​1763)
  • e2e: use taskkill to kill processes on windows (#​1760)
  • config: support nuxt v5 with nitro vite environment (#​1758)
🏡 Chore
  • avoid missing file extension warning in test/examples (#​1775)
  • exempt first-party packages from pnpm minimumReleaseAge (#​1774)
  • replace latest ranges with caret ranges (#​1773)
  • move vite environment api tests to example tests (#​1755)
✅ Tests
  • re-enable bun browser e2e on windows (#​1791)
🤖 CI
  • migrate to uppt for release workflow (#​1792)
🎉 New Contributors
❤️ Contributors
nuxt/ui (@​nuxt/ui)

v4.11.0

Compare Source

Features
Bug Fixes
  • AuthForm: type submit payload with the schema output (#​6816) (795c353)
  • Calendar: correct size scale (#​6832) (29f9890)
  • CommandPalette: always escape search highlight to prevent XSS (#​6741) (2a172ef)
  • components: resolve theme props consistently in form controls (#​6834) (7c74269)
  • ContentToc: prevent list from collapsing (#​6778) (706cfd0)
  • Editor: ignore updates without document changes (#​6807) (7e615e1)
  • Icon: render bundled icons during SSR in Vue (#​6841) (545f9e3)
  • locale: correct native names and tajik language code (#​6823) (e333e8d)
  • locale: correct slide placeholder casing in lb (#​6822) (10ec237)
  • Marquee: use logical properties and drop broken vertical RTL animation (#​6833) (9b08a84)
  • Modal: emit transition events from overlay when scrollable (#​6786) (5afbd5c)
  • Slider: bind form aria attributes on thumbs instead of root (#​6768) (f3c2ac2)
  • Slider: forward aria attributes to the thumb (#​6848) (d6c3802)
  • theme: blank top-level base in applyUnstyled (#​6825) (3e89ea7)
  • theme: keep variants when replacing slot classes in app config (#​6824) (0fabbe5)
  • Theme: merge class from props with the component class (#​6842) (731ff26)
  • theme: replace deprecated bare tailwind aliases (#​6865) (d4f2ca0)
  • theme: respect reduced motion on remaining movement transitions (ce5b1df)
  • theme: unify motion easing and respect prefers-reduced-motion (#​6742) (735b264)
  • Tree: use logical padding for indentation (#​6815) (958a3ba)
Performance Improvements
  • Button/Select/SelectMenu/InputMenu: narrow reactive dependencies (#​6736) (6bd1dfc)
  • components: memoize tv slot invocations with simple args (#​6737) (4200e80)
shikijs/shiki (@​shikijs/core)

v4.4.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vuejs/core (@​vue/compiler-core)

v3.5.42

Compare Source

Bug Fixes
eslint/eslint (eslint)

v10.9.1

Compare Source

v10.9.0

Compare Source

v10.8.1

Compare Source

Bug Fixes

  • 18eb0a7 fix: prevent ASI hazard in no-unused-labels autofix (#​21173) (dongkyu lee)
  • 151ba3f fix: false positives in getter-return and accessor-pairs (#​21163) (Grit)
  • 6898df9 fix: ignore meta-property names in id-denylist (#​21166) (Pixel)
  • 4d7db66 fix: ignore meta-property names in id-match (#​21167) (Pixel)
  • 677214e fix: handle ASI hazards in no-unused-vars removeVar suggestion (#​20935) (kuldeep kumar)

Documentation

  • 7d0cbf8 docs: Update README (GitHub Actions Bot)
  • 0a05812 docs: add missing backticks to no-duplicate-imports.js (#​21183) (Lee Daeun)
  • 678c90b docs: Update README (GitHub Actions Bot)
  • 8a10424 docs: Update README (GitHub Actions Bot)
  • 69bb948 docs: Update README (GitHub Actions Bot)

Chores

unjs/mkdist (mkdist)

v2.4.1

Compare Source

compare changes

🩹 Fixes
  • Consider extension when deduping outputs (f4424fe)
❤️ Contributors

v2.4.0

Compare Source

compare changes

🚀 Enhancements
  • dts: Emit .d.vue.ts as type declaration of .vue files (#​301)
🤖 CI
  • Test against previous lts verison (946852b)
  • Remove install of corepack (73894e6)
  • Bump setup/checkout action versions (8a909da)
❤️ Contributors
actions/node-versions (node)

v24.20.0: 24.20.0

Compare Source

Node.js 24.20.0

v24.19.0: 24.19.0

Compare Source

Node.js 24.19.0

v24.18.1: 24.18.1

Compare Source

Node.js 24.18.1

v24.18.0: 24.18.0

Compare Source

Node.js 24.18.0

v24.17.0: 24.17.0

Compare Source

Node.js 24.17.0

v24.16.0: 24.16.0

Compare Source

Node.js 24.16.0

v24.15.0: 24.15.0

Compare Source

Node.js 24.15.0

v24.14.1: 24.14.1

Compare Source

Node.js 24.14.1

v24.14.0: 24.14.0

Compare Source

Node.js 24.14.0

v24.13.1: 24.13.1

Compare Source

Node.js 24.13.1

v24.13.0: 24.13.0

Compare Source

Node.js 24.13.0

v24.12.0: 24.12.0

Compare Source

Node.js 24.12.0

v24.11.1: 24.11.1

Compare Source

Node.js 24.11.1

v24.11.0: 24.11.0

Compare Source

Node.js 24.11.0

v24.10.0: 24.10.0

Compare Source

Node.js 24.10.0

v24.9.0: 24.9.0

Compare Source

Node.js 24.9.0

v24.8.0: 24.8.0

Compare Source

Node.js 24.8.0

v24.7.0: 24.7.0

Compare Source

Node.js 24.7.0

v24.6.0: 24.6.0

Compare Source

Node.js 24.6.0

v24.5.0: 24.5.0

Compare Source

Node.js 24.5.0

v24.4.1: 24.4.1

Compare Source

Node.js 24.4.1

v24.4.0: 24.4.0

Compare Source

Node.js 24.4.0

v24.3.0: 24.3.0

Compare Source

Node.js 24.3.0

v24.2.0: 24.2.0

Compare Source

Node.js 24.2.0

v24.1.0: 24.1.0

Compare Source

Node.js 24.1.0

v24.0.2: 24.0.2

Compare Source

Node.js 24.0.2

v24.0.1: 24.0.1

Compare Source

Node.js 24.0.1

pnpm/pnpm (pnpm)

v11.24.0: pnpm 11.24

Compare Source

Minor Changes
Patch Changes
  • Fixed pnpm v11 incorrectly reporting confirmModulesPurge as unrecognized when set in pnpm-workspace.yaml. The Rust CLI now identifies the unsupported option as a pnpm v11 setting instead of suggesting an unrelated setting.

  • pnpm install --frozen-lockfile no longer fails with ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE when the pinned pnpm version recorded in pnpm-lock.yaml has to be re-resolved before it can be installed. It runs the pnpm version the lockfile pins and leaves the lockfile unchanged #​14124.

  • Under nodeLinker: hoisted, peer-resolution variants of an injected directory dependency (a file: snapshot) are materialized as separate copies again instead of collapsing onto the first-seen variant. Each copy keeps its own peer-resolved dependency set, so a project pinning one peer version no longer resolves another project's variant — Bit root components with conflicting peers across injected copies rely on this.

  • Fixed pnpm install --merge-git-branch-lockfiles --frozen-lockfile failing with ERR_PNPM_OUTDATED_LOCKFILE when a branch lockfile predates the removal of a dependency, or its move to another dependency group #​13966. A dependency that no project declares anymore is no longer reinstated by the merge, and the packages it was the only path to are dropped with it.

  • Batch workspace publishing accepts a shared scope-specific credential, rejects mismatched credentials for a registry before publishing, and runs the publish and postpublish scripts after each completed registry group pnpm/pnpm#14101.

  • The Rust CLI now honors five settings it recognized but ignored: updateNotifier, legacyDirFiltering, initAuthorName / initAuthorEmail / initAuthorUrl, initLicense, and initVersion. pnpm install and pnpm add check once a day for a newer pnpm and print how to get it (turn it off with updateNotifier: false); a {<dir>} filter selector can go back to matching the subtree below the directory with legacyDirFiltering: true; and pnpm init writes the configured author, license, and version into the package.json it scaffolds. PNPM_CONFIG_INIT_VERSION is now read as well.

    maxsockets, npm's spelling of maxSockets, is no longer ignored: both spellings are read from pnpm-workspace.yaml, the global config file, the environment, and the command line, in that increasing order of precedence — a value passed on the command line now wins even when the two sides spelled the setting differently.

    A lastUpdateCheck timestamp dated in the future — after a clock change, a restored snapshot, or a hand-edited state file — no longer silences the update check until that time comes around.

    legacyDirFiltering no longer reaches the workspace-root selectors pnpm generates for itself: the !{<workspace-root>} exclusion a recursive run / exec / add / test appends, and the {<workspace-root>} inclusion --workspace-root appends. Read as subtree matches they named every project below the root, so a recursive command under the setting selected nothing at all, and --workspace-root pulled in every project below the root instead of the root alone #​14101.

  • pnpm install --frozen-lockfile no longer fails when pnpm-lock.yaml records the pinned pnpm version alongside an engine package the running pnpm does not install it from. An entry pinning another version is still refused, and a plain install rewrites the block #​14124.

v11.23.0: pnpm 11.23

Compare Source

Minor Changes

  • pnpm config get and pnpm config list now show the settings pnpm acts on under their documented names:

    • registries shows the registries pnpm resolves from, merged across every source (.npmrc, pnpm-workspace.yaml, the global config, CLI flags), in the shape the setting is written in: keyed by registry URL, with the default registry declared as the bare @ scope. Built-in routes are included — the @jsr scope and the npmjs and gh prefixes — unless pointed elsewhere. Previously pnpm config get registries printed undefined.
    • update and audit show the effective sections, whichever spelling set them. The deprecated internal spellings (updateConfig, auditConfig, auditLevel) are no longer listed.
    • catalogs shows the complete resolved catalog set — the singular catalog block is its default entry — whichever spelling declared it.
    • The registry and @scope:registry entries show the merged routes rather than raw .npmrc values, so they always agree with the registries view.
  • Settings that no supported pnpm version recognizes get their own warning. A key in the global config file that this version of pnpm does not read is no longer reported with advice to move it to a project-level pnpm-workspace.yaml (where it would be ignored too); the warning now says the setting is not recognized by this version of pnpm, names the pnpm version that does read it when there is one (for example, globalShims is a pnpm v12 setting), and suggests the closest real setting name when the key looks like a typo. Unrecognized and non-camelCase keys in a project's pnpm-workspace.yaml, previously ignored silently, are now reported the same way. pnpm config get <key> and pnpm get <key> no longer print config-load warnings, so a script capturing the value gets the value alone.

  • The importPackage pnpmfile hook is deprecated. pnpm now prints a warning when a pnpmfile defines it, and the hook will be removed in the next major version. It also opts the installation out of the parallel package importer, making installation slower. If you rely on this hook, comment on #​14101.

  • node_modules/.modules.yaml no longer records the registries an install resolved from, and the recorded copy is dropped from the file on the first install that rewrites it.

    It dated from the lockfile format that spelled a dependency's path relative to its registry, where reading an installed tree meant knowing the registries it was installed with. Dependency paths have not carried a registry for several major versions, and the recorded copy outlived its use: pnpm list, pnpm why, and single-project installs preferred it over the project's own configuration, so a project whose registry had changed since its last install was still read through the old one.

    They now use the configured registries, like every other command already did.

  • When enableGlobalVirtualStore is on, every process pnpm spawns for the project (pnpm run, pnpm exec, lifecycle scripts) now receives a NODE_PATH pointing at the project's hoisted node_modules, plus a NODE_OPTIONS --import flag that registers a resolve hook restoring NODE_PATH lookups for ESM imports. Dependencies that import undeclared ("phantom") packages keep resolving under the global virtual store — for both CommonJS and ESM — without installing the @pnpm/plugin-esm-node-path config dependency pnpm/pnpm#9618. Tools run by pnpm dlx resolve such dependencies too: the JS CLI passes them the same environment, while the Rust CLI's dlx cache is self-contained, so its layout already exposes them.

  • A registry can now declare that its abbreviated metadata carries the time field, so resolutionMode: time-based reads the full metadata document only from the registries that need it:

    resolutionMode: time-based
    registries:
      https://npm.internal.example/:
        supportsTimeField: true

    registry.npmjs.org omits time from abbreviated metadata, so a time-based resolution has to fall back to the much larger full document. That fallback used to be all-or-nothing: registrySupportsTimeField answered for every registry at once, so a project resolving from both the public registry and a Verdaccio instance either paid for full metadata everywhere or claimed a time field npmjs does not serve. The answer is now per registry, and registrySupportsTimeField remains the answer for every registry that does not declare one.

    The declaration is also sent to a pnpr server, which applies it to the resolution it runs on the client's behalf.

  • A pnpr resolve request now carries the client's registries the way the registries setting declares them — keyed by URL, with the scopes routed to each, the bare-specifier prefix each answers to, and each one's serverType — in place of the prefix map it used to send.

    The server routes them through the same inversion the config reader runs, so a pnpr-served install resolves a scoped dependency from the registry that scope is routed to, which it previously could not: only the default registry and the prefix-addressed ones reached the server. A declared serverType reaches it too, so the tarball URLs pnpr omits from the lockfile match the ones the client reconstructs.

    Built-in scope routes the project has not pointed elsewhere are not declared, so a pnpr server's allowlist is not asked about npm.jsr.io on requests that resolve no JSR package.

    A registry a request only declares is no longer refused up front for being off the server's allowlist — a client describes its whole configuration, including scopes a given resolve never reaches, so a stray @scope:registry in a developer's ~/.npmrc no longer fails every install against a pnpr server that does not serve it. The boundary moves to the fetch itself: an origin the resolve does reach is refused before the request leaves the server, with the same message.

    This changes the resolve and verify-lockfile request bodies. A pnpr server and its clients have to be on matching versions; the protocol is still experimental and unversioned.

  • The registries setting now declares a registry once, keyed by its URL, with everything about that registry in the entry: how it lays out tarball URLs, the scopes routed to it, and the bare-specifier prefix it answers to.

    registries:
      https://artifactory.example.com/artifactory/api/npm/npm-virtual/:
        serverType: artifactory
        scopes: ['@acme', '@acme-internal']
        prefix: work
    • serverType tells pnpm how the registry lays out its tarball URLs, which decides whether a URL can be omitted from pnpm-lock.yaml:
      • undeclared (the default) — strict. Only the exact canonical URL is treated as reconstructible.
      • npm — the registry behaves like registry.npmjs.org, which also serves a scoped package from its percent-encoded path. Declare this for a faithful mirror or caching proxy of the public registry so its tarball URLs can be omitted too.
      • artifactory — JFrog Artifactory repeats the scope in a scoped package's tarball filename (@acme/widget/-/@acme/widget-1.0.0.tgz) where the npm registry strips it (@acme/widget/-/widget-1.0.0.tgz). Declaring it lets pnpm rebuild that URL, so it is omitted from pnpm-lock.yaml instead of being written out for every scoped package pnpm/get-npm-tarball-url#16.
    • scopes lists the @-prefixed scopes that resolve from this registry. A bare '@' is the scope-less default registry, the one the registry setting names.
    • prefix is the alias a dependency addresses this registry by, as in "foo": "work:^1.0.0".

    The layout is never inferred from the registry URL, so nothing changes unless you declare it; registry.npmjs.org continues to behave as npm without being declared. Because the lockfile depends on serverType, it is read from pnpm-workspace.yaml only — a serverType in the global config.yaml is ignored, so one developer's machine cannot shape a lockfile their collaborators read back with a different layout. Credentials are rejected in this setting, in a key as well as in a field, and still belong in .npmrc. An entry that routes nothing to itself and matches no configured registry is reported as a warning rather than silently ignored.

Migrating

The older registries shape, a map of <scope>: <url> strings, still works and needs no change:

registries:
  '@acme': https://npm.acme.example/

`namedRegistrie

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on Monday"
  • 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.

@pkg-pr-new

pkg-pr-new Bot commented Mar 30, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/@nuxtjs/mdc@476

commit: e7f388a

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 19bb6c4 to aea8810 Compare March 31, 2026 08:58
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies chore(deps): update resolutions mkdist to v2.4.1 Mar 31, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from aea8810 to 26d8a91 Compare April 1, 2026 16:46
@renovate renovate Bot changed the title chore(deps): update resolutions mkdist to v2.4.1 chore(deps): update all non-major dependencies Apr 1, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 15ebb37 to 58bed64 Compare April 8, 2026 13:15
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 9a8dee0 to bd30b0d Compare April 10, 2026 10:39
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from eba4501 to 13e213b Compare April 23, 2026 13:41
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 4ad542d to ea58d4b Compare April 29, 2026 15:38
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 665a065 to 0b881bb Compare May 18, 2026 16:56
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 14 times, most recently from 3f916d6 to 2a68d42 Compare May 25, 2026 09:54
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 4d61988 to 44c6bd1 Compare May 31, 2026 13:32
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