chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #446 · nuxt/scripts

renovate · 2025-04-05T00:27:07Z

This PR contains the following updates:

Package	Change	Type	Update	Pending
@nuxt/devtools-kit (source)	`^3.4.0` → `^3.4.1`	pnpm.catalog.default	patch
@types/geojson (source)	`^7946.0.0` → `^7946.0.16`	peerDependencies	patch
@types/google.maps (source)	`^3.58.1` → `^3.65.4`	peerDependencies	minor
@types/leaflet (source)	`^1.9.21` → `^1.9.22`	pnpm.catalog.default	patch
@types/leaflet (source)	`^1.9.0` → `^1.9.22`	peerDependencies	patch
@types/semver (source)	`^7.7.1` → `^7.8.0`	pnpm.catalog.default	minor
@types/youtube (source)	`^0.1.0` → `^0.3.0`	peerDependencies	minor
Hebilicious/reproduire	`v0.0.9-mp` → `v0.0.9`	action	patch
magicast	`^0.5.3` → `^0.5.4`	pnpm.catalog.default	patch
node	`24` → `24.19.0`	uses-with	minor
oxc-parser (source)	`^0.142.0` → `^0.143.0`	pnpm.catalog.default	minor
pnpm (source)	`11.19.0` → `11.20.0`	packageManager	minor
posthog-js (source)	`^1.409.5` → `^1.410.6`	pnpm.catalog.default	patch	`1.412.0` (+5)
posthog-js (source)	`^1.0.0` → `^1.410.6`	peerDependencies	minor	`1.412.0` (+5)
undici (source)	`^6.27.0` → `^6.28.0`	pnpm.catalog.default	patch

Release Notes

nuxt/devtools (@nuxt/devtools-kit)

`v3.4.1`

Compare Source

🐞 Bug Fixes

devtools: Prevent StateEditor from freezing the page on live state - by @antfubot in #1058 (06249)

View changes on GitHub

Hebilicious/reproduire (Hebilicious/reproduire)

`v0.0.9`

Compare Source

compare changes

unjs/magicast (magicast)

`v0.5.4`

Compare Source

🐞 Bug Fixes

Preserve inner comment when adding a property to an empty object - by @naveentehrpariya in #165 (84cd0)
Handle standalone comments in builders.raw - by @naveentehrpariya in #164 (42dd4)

View changes on GitHub

actions/node-versions (node)

`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

oxc-project/oxc (oxc-parser)

`v0.143.0`

💥 BREAKING CHANGES

067da8c ast: [BREAKING] Store single parameter in TSIndexSignature::parameter (#25154) (camc314)
1bdedd1 ast: [BREAKING] Introduce ExportDeclaration, ExportFromDeclaration (#25095) (camc314)
c917f20 ast: [BREAKING] Introduce ArrowFunctionBody enum (#24987) (camc314)

pnpm/pnpm (pnpm)

`v11.20.0`: pnpm 11.20

Compare Source

Minor Changes

Security fix. Affects projects using namedRegistries on pnpm 11.1.0–11.19.x. It is semi-breaking for those projects — see "If you use named registries" below.
The lockfile recorded no marker for which registry a package came from. Packages were keyed by name@version alone, and entry lookup went through refToRelative(ref, name), so a dependency you declared against one registry could be satisfied by an entry that was actually resolved from another. When two registries served the same name and version, both collapsed onto a single packages: entry and whichever resolved first decided the tarball every consumer got.
That is a package-substitution risk: a package you expect from your private registry could be installed from a different registry that publishes the same name and version, and the lockfile recorded nothing that would let you tell.
Packages resolved from a named registry are now recorded under registry-qualified keys (<name>@<registryName>:<version>, e.g. foo@work:1.0.0), so each registry gets its own entry and the lockfile pins which one a dependency came from.
The lockfile format version is unchanged. Registry-qualified keys appear only for packages resolved from a named registry, so a project that does not use namedRegistries sees no difference, and older pnpm versions keep reading the file.

If you use named registries

Your next non-frozen install re-keys those entries, which shows up as a lockfile diff. Commit it — that diff is the fix being applied. Review it: an entry that moves to a registry you did not expect is worth investigating.

Everyone working on the project should be on this version or newer before you do. An older pnpm reads the re-keyed lockfile fine — frozen installs are unaffected — but it does not produce registry-qualified keys itself, so any install that updates the lockfile writes those entries back to the old shape, and the next install on a current pnpm re-qualifies them. The result is a lockfile that flips back and forth, and while it is in the old shape the project is exposed again. Because the lockfile format version is deliberately unchanged, pnpm cannot detect this and warn you about it.

There is no setting to keep the old behavior: the old shape is the vulnerability.

Tarball URLs that follow the standard registry layout are no longer written to the lockfile for named-registry packages; they are recomputed from the namedRegistries setting on demand.

To use named registries, map your aliases in pnpm-workspace.yaml:

namedRegistries:
work: https://npm.enterprise.example.com/

New built-in `npmjs:` alias

npmjs: now resolves to https://registry.npmjs.org/ with no configuration, alongside the existing gh: alias for GitHub Packages. It pins a dependency to the public registry even when registry points elsewhere, such as an internal proxy:

{ "dependencies": { "left-pad": "npmjs:^1.3.0" } }

npm: cannot do this — it is the alias protocol (npm:<name>@<range>) and resolves through whatever registry points at.

If you mirror or proxy npmjs, point the alias at your mirror:

namedRegistries:
npmjs: https://npm.internal.example.com/

Built-in registry URLs are also the prefixes a lockfile's recorded tarball URL is matched against when pnpm verifies a package. Without the override, an entry whose tarball URL is on registry.npmjs.org is verified against the public registry rather than your mirror. This only affects lockfiles that record such URLs — a canonical URL for your configured registry is omitted from the lockfile and unaffected — and only when a tarball-URL, minimumReleaseAge, or trustPolicy check runs. Overriding the alias is the same escape hatch GHES users already have for gh.

Every alias the lockfile references must stay in namedRegistries: reading an entry whose alias is gone fails with ERR_PNPM_MISSING_NAMED_REGISTRY rather than silently falling back to the default registry, since that would fetch a different package. Renaming an alias re-resolves the packages that used it.

Named registry aliases that shadow a reserved dependency specifier prefix (file, link, workspace, runtime, npm, jsr, ...) are now rejected with ERR_PNPM_RESERVED_NAMED_REGISTRY_NAME instead of being silently shadowed by the corresponding resolver.

pnpm licenses and pnpm sbom now keep the two artifacts apart as well: license records carry the registry alias, and SBOM components carry the purl repository_url qualifier.

Patch Changes

An empty http-proxy, https-proxy, proxy, or no-proxy value — from the .npmrc, pnpm-workspace.yaml, the CLI, or the HTTP_PROXY / HTTPS_PROXY / PROXY / NO_PROXY environment variables — no longer fails the install with ERR_PNPM_INVALID_PROXY. Empty settings read as unset, so a shell exporting HTTP_PROXY= disables the proxy, and an empty proxy= in the .npmrc no longer suppresses HTTPS_PROXY#13533.
proxy=false in the .npmrc or proxy: false in pnpm-workspace.yaml now turns proxying off instead of being read as a proxy host named false. false and null on https-proxy / http-proxy / no-proxy read as unset, and on the command line they are ordinary host names, since a flag carries its value verbatim.
The env lockfile no longer pins @pnpm/exe alongside pnpm when the wanted pnpm version is 12 or newer. From v12 the unscoped pnpm package is itself the native executable, so @pnpm/exe is not published for it and resolving it would fail. The engine identity check now verifies the native binary through whichever package ships it.
lexCompare and nerfDart are now published as @pnpm/text.ordinal-comparator and @pnpm/config.registry-auth-key. Use these instead of @pnpm/util.lex-comparator and @pnpm/config.nerf-dart.
Fixed the order in which pnpm matches a lockfile's recorded tarball URL against known registry URLs. Two registry URLs of equal length were previously ordered arbitrarily, so which one a tarball URL matched could differ between runs.
Dependency resolution is faster: package metadata is now filtered once per packument instead of once per dependency edge when minimumReleaseAge is active, and parsed semver versions and ranges are reused instead of re-parsed on every comparison.
Security: pnpm rebuild now refuses a lockfile whose packages key carries a path traversal in the package name (e.g. ../../../escaped@1.0.0), instead of running that package's lifecycle scripts and linking its bins in a directory outside the virtual store. Such a name is rejected with ERR_PNPM_INVALID_DEPENDENCY_NAME.

Platinum Sponsors

Gold Sponsors

PostHog/posthog-js (posthog-js)

`v1.410.6`

Compare Source

1.410.6

Patch Changes

#4407 6d5e314 Thanks @ioannisj! - Fix session replay shipping one billable recording per session rotation for tabs the user never interacts with. A session born from an idle rotation now holds its buffer until the first user interaction, then ships a recording playable from the session's start; without interaction nothing is sent — a further rotation, stop, opt-out, or page unload discards the held data instead of shipping it. An event trigger match (for example record-on-exception) also releases the hold, since it is explicit intent to record the session.
(2026-08-03)

`v1.410.5`

Compare Source

1.410.5 Patch Changes

#4273 8ec3499 Thanks @felipeatom! - Fix selector-widget surveys being abruptly removed while open when their trigger element is unmounted from the DOM (e.g. a dropdown or menu that hosts the trigger closes). The survey is now kept in place while open and only torn down once the user has closed it. Also fixes a related leak where, if the selector resolved to a different element while the survey was open, the old element's click listener was never removed and kept dispatching the show-widget event for the lifetime of the page.
(2026-08-03)

`v1.410.4`

Compare Source

`v1.410.3`

Compare Source

1.410.3

Patch Changes

#4399 662fb4c Thanks @christiaan-ph! - Conversations widget: bullet and numbered lists in a support reply now keep their markers on host pages with an aggressive CSS reset (for example Tailwind preflight's ol, ul { list-style: none }). The widget renders into the host page's DOM, so the list style is now set inline on <ul>, <ol>, and <li> rather than left to the page's own styles.
(2026-08-03)

`v1.410.2`

Compare Source

`v1.410.1`

Compare Source

1.410.1

Patch Changes

#4386 0854095 Thanks @marandaneto! - Prevent the inline canvas recording worker from requesting an unusable source map from its blob URL.
(2026-08-03)
Updated dependencies [eb0a793]:
- @posthog/core@1.46.3

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.

vercel · 2025-04-05T00:27:09Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
scripts-docs	Error		Aug 5, 2026 7:13am
scripts-playground	Ready	Preview	Aug 5, 2026 7:13am

pkg-pr-new · 2025-07-16T18:29:18Z

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/scripts@446

commit: 84cbbae

vercel · 2025-11-25T02:47:14Z

 "@nuxt/image": "^1.11.0",
 "@nuxt/scripts": "workspace:*",
- "@nuxt/ui": "4.0.0",
+ "@nuxt/ui": "4.2.1",


Suggested change
"@nuxt/ui": "4.2.1",
"@nuxt/ui": "^4.2.1",
The @nuxt/ui dependency is pinned to 4.2.1 without a caret, which is inconsistent with all other dependencies in this file that use flexible versioning with the ^ prefix.
View Details
Analysis
Inconsistent version pinning for @nuxt/ui dependency
What fails: docs/package.json line 20 specifies @nuxt/ui as pinned version 4.2.1 (without caret prefix), while all 13 other dependencies use caret versioning (^) for flexible version constraints within the major version.
How to reproduce:
cat docs/package.json | grep -A 15 '"dependencies"'
Result: Shows "@nuxt/ui": "4.2.1" (pinned) while all surrounding dependencies have caret prefix:
"@nuxt/content": "^3.8.2"
"@nuxt/fonts": "^0.12.1"
"@nuxthq/studio": "^2.2.1"
All other 10 dependencies also use ^ prefix
Expected behavior: According to npm semantic versioning, caret versioning allows compatible updates (minor/patch versions) within a major version. The project consistently uses this pattern for all other dependencies, so @nuxt/ui should be ^4.2.1 to match the established convention and allow patch/minor updates like other dependencies.
Root cause: Automated dependency update (Renovate bot commit 0b37709) preserved the previous pinned format when bumping the version from 4.0.0 to 4.2.1, rather than applying the project's standard caret versioning pattern used throughout the file.

vercel · 2026-01-15T00:37:21Z

- "posthog-js": "^1.0.0"
+ "@types/youtube": "^0.1.2",
+ "@unhead/vue": "^2.1.2",
+ "posthog-js": "^1.321.2"


Suggested change
"posthog-js": "^1.321.2"
"posthog-js": "^1.0.0"
The posthog-js peer dependency constraint changed from ^1.0.0 to ^1.321.2, which is unusually restrictive and appears unintentional given the patch version bump in devDependencies (1.321.1 → 1.321.2).
View Details
Analysis
Overly restrictive posthog-js peer dependency breaks backward compatibility
What fails: The posthog-js peer dependency constraint in package.json was changed from ^1.0.0 to ^1.321.2 (commit 1536ad2), restricting supported versions to 1.321.2+ and rejecting all prior versions (1.0.0-1.321.1) that would previously install.
How to reproduce:
# User has posthog-js 1.200.0 installed (legitimate version under old ^1.0.0 constraint) npm install @nuxt/scripts # After update, npm now rejects this version because 1.200.0 does not satisfy ^1.321.2
Result: npm/pnpm install fails with: "posthog-js@1.200.0 not satisfied by ^1.321.2"
Expected: The peer dependency should remain at ^1.0.0 (or similar permissive constraint) since:
Code only uses posthog.init() and basic config options (api_host, capture_pageview, disable_session_recording) available since 1.0.0
The devDependency update was only a patch bump (1.222.0 → 1.321.2), not a major version requiring API changes
Peer dependencies should be permissive to maximize compatibility
Semantic versioning guidance indicates patch/minor version updates within the same major version should be backward compatible
This change appears to be an error from automated dependency update tooling (Renovate) that applied the same pinpoint version to both devDependencies and peerDependencies.

socket-security · 2026-04-29T17:16:38Z

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

socket-security · 2026-08-04T09:34:51Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality
posthog-js@1.412.0 ⏵ 1.410.6	⁺²⁹	⁺¹
@types/semver@7.8.0
oxc-parser@0.142.0 ⏵ 0.143.0		⁺¹
magicast@0.5.4

View full report

renovateBotforce-pushed the renovate/all-minor-patch branch from 9c4e39b to 5bfebeaCompare April 5, 2025 00:30

vercelBotdeployed to Preview – scripts-playground April 5, 2025 00:37 View deployment

vercelBotdeployed to Preview – scripts-docs April 5, 2025 00:40 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 5bfebea to 7804f68Compare April 6, 2025 09:08

renovateBot changed the title ~~chore(deps): update resolutions typescript to v5.8.3~~chore(deps): update all non-major dependenciesApr 6, 2025

vercelBotdeployed to Preview – scripts-docs April 6, 2025 09:10 View deployment

vercelBotdeployed to Preview – scripts-playground April 6, 2025 09:12 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 7804f68 to 2d975ffCompare April 7, 2025 04:48

vercelBotdeployed to Preview – scripts-docs April 7, 2025 04:51 View deployment

vercelBotdeployed to Preview – scripts-playground April 7, 2025 04:53 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 2d975ff to 0104ff1Compare April 7, 2025 08:22

vercelBotdeployed to Preview – scripts-playground April 7, 2025 08:24 View deployment

vercelBotdeployed to Preview – scripts-docs April 7, 2025 08:26 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 0104ff1 to 8120e32Compare April 7, 2025 15:15

vercelBotdeployed to Preview – scripts-playground April 7, 2025 15:17 View deployment

vercelBotdeployed to Preview – scripts-docs April 7, 2025 15:20 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 8120e32 to 5ec9f5eCompare April 7, 2025 18:22

vercelBotdeployed to Preview – scripts-docs April 7, 2025 18:29 View deployment

vercelBotdeployed to Preview – scripts-playground April 7, 2025 18:31 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 5ec9f5e to efcb3b7Compare April 8, 2025 08:39

vercelBotdeployed to Preview – scripts-playground April 8, 2025 08:42 View deployment

vercelBotdeployed to Preview – scripts-docs April 8, 2025 08:44 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from efcb3b7 to 1a61aecCompare April 10, 2025 00:28

vercelBotdeployed to Preview – scripts-playground April 10, 2025 00:30 View deployment

vercelBotdeployed to Preview – scripts-docs April 10, 2025 00:33 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 1a61aec to cf8e7f8Compare April 10, 2025 09:47

vercelBotdeployed to Preview – scripts-playground April 10, 2025 09:50 View deployment

vercelBotdeployed to Preview – scripts-docs April 10, 2025 09:52 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from cf8e7f8 to 2b13cf8Compare April 11, 2025 01:12

vercelBotdeployed to Preview – scripts-playground April 16, 2025 07:26 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 16, 2025 07:27 Failure

renovateBotforce-pushed the renovate/all-minor-patch branch from 6132302 to 360e116Compare April 16, 2025 14:05

vercelBotdeployed to Preview – scripts-playground April 16, 2025 14:07 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 16, 2025 14:08 Failure

renovateBotforce-pushed the renovate/all-minor-patch branch from 360e116 to aa97a8bCompare April 17, 2025 00:59

vercelBotdeployed to Preview – scripts-playground April 17, 2025 01:02 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 17, 2025 01:03 Failure

renovateBotforce-pushed the renovate/all-minor-patch branch from aa97a8b to 714cf9dCompare April 17, 2025 08:46

vercelBotdeployed to Preview – scripts-playground April 17, 2025 08:48 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 17, 2025 08:49 Failure

renovateBotforce-pushed the renovate/all-minor-patch branch from 714cf9d to bdbb60cCompare April 17, 2025 18:14

vercelBothad a problem deploying to Preview – scripts-docs April 17, 2025 18:15 Failure

vercelBotdeployed to Preview – scripts-playground April 17, 2025 18:17 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from bdbb60c to 9343bf3Compare April 18, 2025 20:28

vercelBothad a problem deploying to Preview – scripts-docs April 18, 2025 21:10 Failure

vercelBotdeployed to Preview – scripts-playground April 18, 2025 21:12 View deployment

renovateBotforce-pushed the renovate/all-minor-patch branch from 9343bf3 to fb7fea7Compare April 21, 2025 12:46

vercelBotdeployed to Preview – scripts-playground April 21, 2025 12:48 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 21, 2025 12:49 Failure

renovateBotforce-pushed the renovate/all-minor-patch branch from fb7fea7 to 556aaaeCompare April 21, 2025 16:40

vercelBotdeployed to Preview – scripts-playground April 21, 2025 16:42 View deployment

vercelBothad a problem deploying to Preview – scripts-docs April 21, 2025 16:43 Failure

vercelBot reviewed Sep 20, 2025
View reviewed changes

Comment threadpnpm-lock.yaml Outdated

vercelBot reviewed Nov 25, 2025
View reviewed changes

vercelBot reviewed Jan 15, 2026
View reviewed changes

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

Navigation Menu

Uh oh!

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

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

renovateBot commented Apr 5, 2025•
edited
Loading

Uh oh!

vercelBot commented Apr 5, 2025•
edited
Loading

Uh oh!

pkg-pr-newBot commented Jul 16, 2025•
edited
Loading

Uh oh!

Uh oh!

vercelBotNov 25, 2025

Uh oh!

vercelBotJan 15, 2026

Uh oh!

socket-securityBot commented Apr 29, 2026•
edited
Loading

Uh oh!

socket-securityBot commented Aug 4, 2026•
edited
Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovateBot commented Apr 5, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

🐞 Bug Fixes

🐞 Bug Fixes

v24.19.0: 24.19.0

v24.18.1: 24.18.1

v24.18.0: 24.18.0

v24.17.0: 24.17.0

v24.16.0: 24.16.0

v24.15.0: 24.15.0

v24.14.1: 24.14.1

v24.14.0: 24.14.0

v24.13.1: 24.13.1

v24.13.0: 24.13.0

v24.12.0: 24.12.0

v24.11.1: 24.11.1

v24.11.0: 24.11.0

v24.10.0: 24.10.0

v24.9.0: 24.9.0

v24.8.0: 24.8.0

v24.7.0: 24.7.0

v24.6.0: 24.6.0

v24.5.0: 24.5.0

v24.4.1: 24.4.1

v24.4.0: 24.4.0

v24.3.0: 24.3.0

v24.2.0: 24.2.0

v24.1.0: 24.1.0

v24.0.2: 24.0.2

v24.0.1: 24.0.1

💥 BREAKING CHANGES

v11.20.0: pnpm 11.20

Minor Changes

If you use named registries

New built-in npmjs: alias

Patch Changes

Platinum Sponsors

Gold Sponsors

1.410.6

Patch Changes

1.410.5

Patch Changes

1.410.3

Patch Changes

1.410.1

Patch Changes

Configuration

Uh oh!

vercelBot commented Apr 5, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pkg-pr-newBot commented Jul 16, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

vercelBotNov 25, 2025

Choose a reason for hiding this comment

Analysis

Inconsistent version pinning for @nuxt/ui dependency

Uh oh!

vercelBotJan 15, 2026

Choose a reason for hiding this comment

Analysis

Overly restrictive posthog-js peer dependency breaks backward compatibility

Uh oh!

socket-securityBot commented Apr 29, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-securityBot commented Aug 4, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

renovateBot commented Apr 5, 2025•
edited
Loading

`v24.19.0`: 24.19.0

`v24.18.1`: 24.18.1

`v24.18.0`: 24.18.0

`v24.17.0`: 24.17.0

`v24.16.0`: 24.16.0

`v24.15.0`: 24.15.0

`v24.14.1`: 24.14.1

`v24.14.0`: 24.14.0

`v24.13.1`: 24.13.1

`v24.13.0`: 24.13.0

`v24.12.0`: 24.12.0

`v24.11.1`: 24.11.1

`v24.11.0`: 24.11.0

`v24.10.0`: 24.10.0

`v24.9.0`: 24.9.0

`v24.8.0`: 24.8.0

`v24.7.0`: 24.7.0

`v24.6.0`: 24.6.0

`v24.5.0`: 24.5.0

`v24.4.1`: 24.4.1

`v24.4.0`: 24.4.0

`v24.3.0`: 24.3.0

`v24.2.0`: 24.2.0

`v24.1.0`: 24.1.0

`v24.0.2`: 24.0.2

`v24.0.1`: 24.0.1

`v11.20.0`: pnpm 11.20

New built-in `npmjs:` alias

vercelBot commented Apr 5, 2025•
edited
Loading

pkg-pr-newBot commented Jul 16, 2025•
edited
Loading

socket-securityBot commented Apr 29, 2026•
edited
Loading

socket-securityBot commented Aug 4, 2026•
edited
Loading