Vercel deployment files with version 2.20.1 because of the size of query-engine-rhel-openssl-1.0.x has increased
See original GitHub issueDeploying to vercel with prisma 2.20.1 may result in the following error:
Error: The Serverless Function "" is XX.Xmb which exceeds the maximum size limit of 50mb. Learn More: https://vercel.link/serverless-function-size
To solve it for now you can use prisma 2.19.0 in which the size of query-engine-rhel-openssl-1.0.x is about 25MB whereas the same engine has a size of about 45MB in version 2.20.1.
There is already an issue for this aimed at serverless framework. But others working with Vercel might overlook that one, therefore this separate issue.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:19 (12 by maintainers)
Top Results From Across the Web
Errors – Vercel Docs
A list of errors provided by Vercel CLI or the REST API, with details on how they occur and how to resolve them....
Read more >Limits – Vercel Docs
The maximum number of files that can be uploaded when creating a CLI Deployment is 15,000 for source files. Deployments that contain more...
Read more >Project Config with vercel.json
The vercel.json configuration file lets you configure, and override the default behavior of Vercel from within your project. This includes settings for:.
Read more >Troubleshoot a Build – Vercel Docs
If the build exceeds this time, the deployment will be canceled and the error will be shown on the Deployment's Build logs. If...
Read more >Caching – Vercel Docs
Note that Vercel won't allow bypassing the cache for static files. ... for images will persist between deployments because they're treated differently from ......
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 FreeTop 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
Top GitHub Comments
@janpio Of course it turned out to be my bad 😄 It was related to
binaryTargets
. We had a lot of binaryTargets because some of our developers work on M1 and our prisma config looks in this waybinaryTargets = ["native", "debian-openssl-1.1.x", "linux-arm64-openssl-1.1.x"]
Probably the best solution is to set it via the environment variable. Anyway, this was the reason for the package size.
@janpio okay I will do it, thanks!