Next.js 14.0.4-canary.36 breaks build of turborepo on Vercel - Works up to 14.0.4-canary.35
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 185
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've been struggling with a A Serverless Function has exceeded the unzipped maximum size of 250 MB error on my monorepo.
It uses turborepo and has been working fine (deploying on Vercel) for the past couple of years.
My serverless functions are including the /.next folder which is over 900mb uncompressed. It doesn't make any sense to me.
When the build is triggered via a commit with the GitHub/Vercel integration, then the build fails. If I click Redeploy on Vercel, the build works.
I believe the issue stems from the fact that Next.js 14.0.4-canary.36 has this change applied to it.
More info on the issue can be found here.
Any help is appreciated. Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the GitHub/Vercel-triggered build with Next.js 14.0.4-canary.36 and compare it with canary.35, focusing on the oversized /.next folder mentioned in the report. Check the linked vercel/nft change and related Next.js issue; done means the serverless functions no longer exceed 250 MB and the integrated deployment succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js
- Domain
- build-system, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100