Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Exceeds maximum size limit of 50mb
See original GitHub issueHi,
Since the latest release (0.23), all deployments are failing with the following message :
I rolled back to 0.22.1 and the deployment never goes over 49.99 mb.
Was this limit handled before and this change is expected?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Exceeding size limits (50mb) for Serverless Functions #103
The maximum size for a Serverless Function is 50 MB and the maximum unzipped size is 250 MB including layers which are automatically...
Read more >NextJs: The Serverless Function exceeds the maximum ...
So 50.55MB is likely the size of your current entire build. I'm researching how to only include certain files within the vercel.json but ......
Read more >Nuxt app won't deploy to vercel because 'The Serverless ...
The Serverless Function "index" is 68.73mb which exceeds the maximum size limit of 50mb.
Read more >Attachment size exceeds the allowable limit error - Outlook
You receive this error message because Outlook 2013 and later versions have a default attachment size limit of 20 megabytes (20480 KB) for ......
Read more >NextJs: The Serverless Function exceeds the maximum size ...
Coding example for the question NextJs: The Serverless Function exceeds the maximum size limit of 50mb-Reactjs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue is the latest version of npm, which has a bug with installing dependencies in a symlink. Previously we pinned to an older version of the vercel build tools and raised the issue. See https://github.com/nuxt/vercel-builder/pull/636 for a description of the problem.
Current workarounds are:
Actually, this is still relevant.