Open valentinpalkovic opened 6 days ago
@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 👍
Hi @terrymun
Thank you very much for providing this detailed information! We will take a look as soon as we are able to work on this issue.
@valentinpalkovic Really appreciate your work with keeping Storybook updated with the latest release of next :) thanks for the update! If you need any further examples or need us to test something out for you, feel free to reach out.
For the Next15 release. It looks like the next/dist/client/components/headers file was moved to next/headers
Describe the bug
Next.js 15 is now stable.
Investigate the following topics:
next/dynamic
in Storybook