chore(deps): bump @storybook-vue/nuxt to latest

[cylewaitforit]

🔗 Linked issue

🧭 Context

The latest version of @storybook-vue/nuxt published to npm is not fully compatible with Storybook 10, Nuxt 4, or Vite 8.

This PR updates the version to the latest merged PR for that package using pkg.pr.new.

📚 Description

Grabbed pkg.pr.new version from latest merged PR for @storybook-vue/nuxt and removed the override set to force Storybook to version 10.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	May 1, 2026 4:25pm
npmx.dev	Ready	Preview, Comment	May 1, 2026 4:25pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		May 1, 2026 4:25pm

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

Chores

• Updated dependency catalogue configuration for improved version resolution.

Walkthrough

The pnpm-workspace.yaml configuration file has been updated to change the Storybook Nuxt integration catalogue entry from version 9.0.1 to a pre-release version 1021 using a pkg.pr.new URL, and removes the explicit workspace override for Storybook ^10.3.1.

Changes

Cohort / File(s)	Summary
Storybook Configuration pnpm-workspace.yaml	Updated Storybook Nuxt integration catalogue reference to use pkg.pr.new URL for @storybook-vue/nuxt@1021 instead of 9.0.1 version, and removed the workspace overrides entry for storybook: ^10.3.1.

Suggested reviewers

• JReinhold
• ghostdevv

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: bumping @storybook-vue/nuxt to the latest version, which is the primary objective of the PR.
Description check	✅ Passed	The description is directly related to the changeset, explaining the compatibility issues with the previous version and the rationale for using pkg.pr.new to obtain the latest merged PR version.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​shikijs/​markdown-exit@​4.0.2
	@​types/​sanitize-html@​2.16.1
	@​unocss/​nuxt@​66.6.7
	@​vueuse/​shared@​14.2.1
	@​takumi-rs/​core@​1.0.9
	@​takumi-rs/​wasm@​1.0.9
	@​types/​semver@​7.7.1
	@​nuxt/​scripts@​1.0.1
	@​shikijs/​themes@​4.0.2
	@​vueuse/​core@​14.2.1
	@​vueuse/​router@​14.2.1
	@​voidzero-dev/​vite-plus-test@​0.1.16
	@​unocss/​preset-wind4@​66.6.7
	@​types/​validate-npm-package-name@​4.0.2
	@​storybook/​addon-a11y@​10.3.5
	@​shikijs/​langs@​4.0.2
	@​nuxt/​test-utils@​4.0.3
	@​vitest/​coverage-v8@​4.1.5
	@​nuxtjs/​color-mode@​4.0.0
	@​types/​node@​24.12.0
	@​nuxtjs/​html-validator@​2.1.0
	@​vite-pwa/​assets-generator@​1.0.2
	@​vueuse/​nuxt@​14.2.1
	@​nuxt/​fonts@​0.14.0
	@​vueuse/​integrations@​14.2.1
	@​vue/​test-utils@​2.4.6
	@​vite-pwa/​nuxt@​1.1.1
	@​storybook/​addon-themes@​10.3.5
	@​nuxtjs/​i18n@​10.2.4
	@​nuxtjs/​mdc@​0.20.2
	@​nuxt/​ui@​4.5.1
	@​playwright/​test@​1.58.2
	@​storybook/​addon-docs@​10.3.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @storybook/builder-vite is 72.0% likely obfuscated Confidence: 0.72 Location: Package overview From: pnpm-lock.yaml → npm/@storybook/builder-vite@10.3.4 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@storybook/builder-vite@10.3.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @voidzero-dev/vite-plus-core is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/@voidzero-dev/vite-plus-test@0.1.16 → npm/@voidzero-dev/vite-plus-core@0.1.16 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@voidzero-dev/vite-plus-core@0.1.16. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

e18e dependency analysis

No dependency warnings found.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

🧹 Nitpick comments (1)

pnpm-workspace.yaml (1)

20-27: Consider moving to a published package version when available.

This catalogue entry currently uses a preview release from pkg.pr.new, which is designed for development and testing rather than production use. Whilst pkg.pr.new packages do not expire and are persistent, they lack the stability guarantees of officially published releases. Since @storybook-vue/nuxt is a development dependency, the current approach is functional; however, plan to transition to a published version once it becomes available to align with standard dependency practices.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pnpm-workspace.yaml` around lines 20 - 27, The storybook catalogue entry uses
a preview registry URL for `@storybook-vue/nuxt`; replace the pkg.pr.new reference
with the official published version specifier (e.g., a semver like '^x.y.z' or
the matching Storybook release) in the storybook dependency block where
'@storybook-vue/nuxt' is declared, update the lockfile by running the package
manager install, and ensure the other storybook addons remain
version-compatible.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@pnpm-workspace.yaml`:
- Around line 20-27: The storybook catalogue entry uses a preview registry URL
for `@storybook-vue/nuxt`; replace the pkg.pr.new reference with the official
published version specifier (e.g., a semver like '^x.y.z' or the matching
Storybook release) in the storybook dependency block where '@storybook-vue/nuxt'
is declared, update the lockfile by running the package manager install, and
ensure the other storybook addons remain version-compatible.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3b58cd7a-fd30-4aa2-9daa-9d1830853123

📥 Commits

Reviewing files that changed from the base of the PR and between 5eab00c and 5c552ed.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• pnpm-workspace.yaml