[Bug]: Investigate Next.js v15 features

[valentinpalkovic]

Describe the bug

Next.js 15 is now stable.

Investigate the following topics:

• I am concerned that people would like to use the React Compiler and will therefore opt-in for babel and opt-out from Next.js’ custom SWC compiler. The experimental-nextjs-vite framework currently only supports SWC, and not babel. It wouldn’t be hard to add babel support, though.
• https://nextjs.org/blog/next-15#executing-code-after-a-response-with-unstable_after-experimental will very likely not work out of the box in Storybook.
• https://nextjs.org/blog/next-15#support-for-nextconfigts might not work out of the box in Storybook
• [Breaking] Disallow using ssr: false option with next/dynamic in Server Components - could break usage of next/dynamic in Storybook

[terrymun]

@valentinpalkovic Thanks for looking into this! I have personally been experimenting with next@15 with storybook (using webpack under the hood), and the only major issue I'm running into is the invalid paths that @storybook/nextjs tries to use when accessing server-related internals on next.js.

If this sounds familiar to you, that's because I've opened a related issue #29380 some days ago... but I've had time to fully try to debug the issue today and finally found the root cause + create a reproducible example for you to work with.

Apologies in advance if I end up hijacking/derailing the purpose of this ticket, feel free to remove this comment so the issue stays on track 👍