Verify breaking changes and Next.js 15 compatibility for vite-plugin-storybook-nextjs v3.

This is a major version bump (2.1.0-canary → 3.0.0) with unknown breaking changes. The project uses Next.js 15.2.3, which itself has breaking changes (async Request APIs). The PR checklist shows all test types unchecked and no manual testing steps provided, which is risky for a major dependency upgrade.

Please verify and document:

1. Breaking changes in v3: What breaking changes exist in vite-plugin-storybook-nextjs v3.0.0?
2. Next.js 15 compatibility: Is v3 tested and compatible with Next.js 15.2.3?
3. Code migration needs: Does the framework code incode/frameworks/nextjs-vite/ require updates to work with v3?
4. Test coverage: Why are all automated tests unchecked? What testing was performed locally?

I'll search for the v3 release notes to understand the scope of changes:The search results provide some context but don't clearly show v3.0.0 breaking changes. Let me search more specifically:Based on the search results, I found that the vite-plugin-storybook-nextjs was updated to 2.0.7 in an earlier release, and the current PR updates it to 3.0.0, which is a major version bump. The search results show various NextJS-Vite issues but don't provide explicit breaking changes documentation. Let me check if there are any code changes required in the framework package itself:Let me now complete the review based on what I've gathered:

I'll gather the necessary information to verify the review comment about this vite-plugin-storybook-nextjs upgrade.

---🏁 Script executed:```shell#!/bin/bash# Check if there are any imports or usages of vite-plugin-storybook-nextjs in the framework code# to determine if code changes are needed for v3 upgradefind code/frameworks/nextjs-vite -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" \) -exec grep -l "vite-plugin-storybook-nextjs" {} \;

Length of output: 135

🌐 Web query:

vite-plugin-storybook-nextjs v3.0.0 release notes breaking changes

💡 Result:

v3.0.0 (released 2025‑10‑24) — breaking change: requires/supports Next.js 16 (See release note). [1]

Sources
[1] GitHub — vite-plugin-storybook-nextjs release v3.0.0.

🌐 Web query:

vite-plugin-storybook-nextjs Next.js 15 compatibility

💡 Result:

Short answer: partially — the plugin declares support for Next.js >= 14.1.0, but Next.js 15 introduced breaking changes that currently cause problems in the Storybook + Vite toolchain (module resolution, compiled React paths, test/Vitest issues, plus other Next‑15 behaviour). Expect some features to work but others (Vitest addon, certain Next 15 internals like compiled React subpaths, some server‑component/runtime features) to fail or need workarounds. [1][2][3]

Details / references:

• vite-plugin-storybook-nextjs README (requires Next.js v14.1.0 or higher). [1]
• Storybook maintainers tracking Next.js 15 investigation and known incompatibilities. [2]
• Reported bug where Storybook/Vitest fails in Next.js 15 because Next compiles React into internal paths (causes module resolution errors). Workarounds (for now) include using Storybook UI testing instead of the Vitest addon. [3]

If you want, I can:

• check the exact versions in your project and suggest a concrete configuration/workaround, or
• search for any newly released fixes/PRs that target Next.js 15 compatibility.

I found a critical issue. Let me verify the Next.js version in the project:

---🏁 Script executed:```shell#!/bin/bash# Check the Next.js version in code/frameworks/nextjs-vite/package.jsongrep -A 1 '"next"' code/frameworks/nextjs-vite/package.json | head -5

Length of output: 89