-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template Studio Fail on Vercel deployment #1549
Comments
Hey! Happy to help out here. So we actually host this template demo on Vercel (https://studio.tailwindui.com) and it's deploying successfully. The issue here might be related to Two quick questions:
Thanks! |
Hi there! So I went on a little excavation and guess what? You’re right, it’s from pnpm, and yarn sails smoothly. But oh boy, try |
Good to know, saving this here to look at later: ➜ studio git:(main) ✗ pnpm up --latest
WARN deprecated @leafac/html@3.0.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Already up to date
WARN Issues with peer dependencies found
.
├─┬ @mdx-js/loader 3.0.0
│ └── ✕ missing peer webpack@>=5
├─┬ autoprefixer 10.4.16
│ └── ✕ missing peer postcss@^8.1.0
└─┬ @leafac/rehype-shiki 2.2.1
└── ✕ unmet peer shiki@^0.11.1: found 0.14.7
Peer dependencies that should be installed:
postcss@^8.1.0 webpack@>=5
Progress: resolved 553, reused 528, downloaded 0, added 0, done
Done in 6.1s |
Hey! So there are three things at play here: First, Second, older versions of PNPM don't install peer dependencies by default. This is what caused the warnings / errors about postcss and webpack. NPM changed this in v7 in Oct 2020 and PNPM finally changed this in v8 to align with NPM in May 2023. We don't list Third, we had an override for using a later version of The updated template is available for download but you can make these changes — in addition to upgrading pnpm: Change the version of - "shiki": "^0.14.7",
+ "shiki": "^0.11.1", Pin - "sharp": "^0.33.1"
+ "sharp": "0.33.1" At the bottom, remove the overrides section completely: - },
+ }
- "overrides": {
- "@leafac/rehype-shiki": {
- "shiki": ">=0.11.1"
- }
- } Hope that helps! ✨ |
Template
Describe the bug
During the deployment process on Vercel, the build fails with a
RangeError: Maximum call stack size exceeded
error. This error occurs during the finalizing page optimization stage. The build works perfectly in a local environment (local build and serve), but consistently fails on Vercel deployment.To Reproduce
Steps to reproduce the behavior:
the build process via Vercel's deployment logs.
3. Observe the build failure with the specific error message
RangeError: Maximum call stack size exceeded
.Expected behavior
The expectation is for the build process to complete successfully on Vercel as it does locally, without encountering a stack overflow error.
Screenshots
N/A (Logs provided in the description should suffice for the error tracing)
Browser/Device (if applicable)
Additional context
The text was updated successfully, but these errors were encountered: