Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 28, 2025

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


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.

@vercel
Copy link

vercel bot commented Apr 28, 2025

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

Project Deployment Preview Comments Updated (UTC)
scripts-docs Error Error Dec 3, 2025 3:16pm
scripts-playground Ready Ready Preview Comment Dec 3, 2025 3:16pm

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from d75b7bd to ee7ee82 Compare May 18, 2025 03:57
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ee7ee82 to 52acbc0 Compare May 18, 2025 08:57
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 52acbc0 to b82c990 Compare June 2, 2025 08:16
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from b82c990 to c4676e0 Compare June 3, 2025 12:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from c4676e0 to f983472 Compare July 6, 2025 03:35
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from f983472 to 530fe10 Compare July 6, 2025 11:02
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 530fe10 to 367533e Compare July 17, 2025 07:44
@pkg-pr-new
Copy link

pkg-pr-new bot commented Jul 17, 2025

Open in StackBlitz

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

commit: 02f8116

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 30fbf8b to 0f47560 Compare September 25, 2025 17:32
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 0f47560 to c2c6dd3 Compare October 7, 2025 21:55
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from c2c6dd3 to 8d6f04b Compare October 7, 2025 22:45
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 8d6f04b to ae08de2 Compare October 13, 2025 06:07
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ae08de2 to b8317d2 Compare October 13, 2025 08:00
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from b8317d2 to 5533273 Compare October 21, 2025 20:09
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 5533273 to 84056c8 Compare November 10, 2025 22:32
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 84056c8 to 9eff4eb Compare November 18, 2025 23:27
'@nuxt/devtools-ui-kit@2.7.0':
resolution: {integrity: sha512-sKe1pLsEfTydefK/Ijr54lId32zOzOKffVbDbtEcwXDs96rHI55Vdo+I6PDqKNflvEcQgXdKArX3bGUHssFQvg==}
peerDependencies:
'@nuxt/devtools': 2.7.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Peer dependency version mismatch: @nuxt/devtools-ui-kit@2.7.0 declares @nuxt/devtools: 2.7.0 as a peer dependency, but @nuxt/devtools@3.1.1 is installed instead.

View Details
📝 Patch Details
diff --git a/client/package.json b/client/package.json
index c0a67e6..2f1913f 100644
--- a/client/package.json
+++ b/client/package.json
@@ -13,7 +13,7 @@
   "devDependencies": {
     "@iconify-json/carbon": "^1.2.14",
     "@nuxt/devtools-kit": "^2.6.5",
-    "@nuxt/devtools-ui-kit": "^2.6.5",
+    "@nuxt/devtools-ui-kit": "^3.1.1",
     "@nuxt/kit": "^4.1.3",
     "nuxt": "^4.1.3",
     "vue": "^3.5.22",
diff --git a/package.json b/package.json
index 39eb7f1..095606a 100644
--- a/package.json
+++ b/package.json
@@ -120,7 +120,7 @@
   },
   "devDependencies": {
     "@nuxt/devtools-kit": "^2.6.5",
-    "@nuxt/devtools-ui-kit": "^2.6.5",
+    "@nuxt/devtools-ui-kit": "^3.1.1",
     "@nuxt/eslint-config": "^1.9.0",
     "@nuxt/module-builder": "^1.0.2",
     "@nuxt/scripts": "workspace:*",

Analysis

Peer dependency version mismatch: @nuxt/devtools-ui-kit@2.7.0 vs @nuxt/devtools@3.1.1

What fails: Package.json declares @nuxt/devtools-ui-kit: ^2.6.5 which resolves to v2.7.0, but that version has a peer dependency requirement of @nuxt/devtools: 2.7.0 exactly. However, the lock file installs @nuxt/devtools@3.1.1 instead, creating a major version mismatch that violates the peer dependency constraint.

How to reproduce:

# The issue is visible in pnpm-lock.yaml at line 863-872:
# @nuxt/devtools-ui-kit@2.7.0 declares:
#   peerDependencies:
#     '@nuxt/devtools': 2.7.0
# But @nuxt/devtools@3.1.1 is the installed version (no 2.7.0 exists in lock)
grep -A 3 "@nuxt/devtools-ui-kit@2.7.0" pnpm-lock.yaml
grep "@nuxt/devtools@3.1.1" pnpm-lock.yaml

Result: pnpm installs with warnings about unmet peer dependencies. While the project has strict-peer-dependencies=false which allows installation to succeed, the version mismatch indicates an incomplete dependency update when @nuxt/devtools was bumped to v3.x.

Expected: @nuxt/devtools-ui-kit should be upgraded to v3.1.1 which declares @nuxt/devtools: 3.1.1 as its peer dependency, matching the installed version of @nuxt/devtools@3.1.1.

Fix applied: Updated @nuxt/devtools-ui-kit from ^2.6.5 to ^3.1.1 in both root package.json and client/package.json per npm registry documentation which shows v3.1.1 requires @nuxt/devtools@3.1.1.

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.

1 participant