You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have my portfolio site built with nextjs 14 and deployed on vercel. I set up storybook in my project using the next js guide in the docs - simply ran npx storybook@latest init.
It seems that the storybook install causes my build on vercel to fail. My deployment shows this error in the build logs RangeError: Maximum call stack size exceeded. I have tested that resetting to the commit before setting up storybook allows the deployment to work fine. I will paste the full build logs below along with my main.ts storybook file and package.json
This is specific to vercel as redeploying the same repo on netlify works fine. It seems to be an issue with how vercel traces files during build but I am at a loss on how to debug this. Posting this incase anyone else has set up storybook in a similar environment and run into this issue and can help me out. I would think this is a fairly common setup (storybook + next 14 + vercel), so I must be doing something wrong on my end.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
I have my portfolio site built with nextjs 14 and deployed on vercel. I set up storybook in my project using the next js guide in the docs - simply ran
npx storybook@latest init
.here is a link to the repo: https://github.com/nirav-v/next-portfolio
It seems that the storybook install causes my build on vercel to fail. My deployment shows this error in the build logs
RangeError: Maximum call stack size exceeded
. I have tested that resetting to the commit before setting up storybook allows the deployment to work fine. I will paste the full build logs below along with my main.ts storybook file and package.jsonThis is specific to vercel as redeploying the same repo on netlify works fine. It seems to be an issue with how vercel traces files during build but I am at a loss on how to debug this. Posting this incase anyone else has set up storybook in a similar environment and run into this issue and can help me out. I would think this is a fairly common setup (storybook + next 14 + vercel), so I must be doing something wrong on my end.
Additional information
package.json
Storybook main.ts file
Vercel Build Logs:
Create a reproduction
No response
Beta Was this translation helpful? Give feedback.
All reactions