Netlify Request must be smaller than 69905067 bytes for the CreateFunction operation
See original GitHub issueNot exactly sure where the documentation lives so I figured here would be the next best place to leave an issue.
netlify
deployment documentation is missing a step. When trying to deploy today I kept receiving this error
Request must be smaller than 69905067 bytes for the CreateFunction operation
After a bunch of googling I couldn’t find a real answer so I went back to the documentation. Still no luck. Luckily @cannikin has those amazing 4k godlike quality videos. He mentions needing the BINARY_TARGET
env variable to be set on netlify
so that prisma
knows to compile to the right target. And then everything deployed smoothly.
So I think it would be a nice addition to add this to the tutorial/text documentation and in the meantime, I put the error in the issue title in case anyone comes here looking.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Request must be smaller than 69905067 bytes for the ...
Request must be smaller than 69905067 bytes for the CreateFunction operation. Any insight on what could be causing this error?
Read more >Functions: request must be smaller than 69905067 bytes ...
I suddenly receive this error while building the website. Not sure why though, because all the previous builds were deployed and functioning ...
Read more >Error: Request must be smaller than 69905067 bytes for ...
I am trying to upload a zipped function but getting Request must be smaller than 69905067 bytes for the CreateFunction operation .
Read more >Request must be smaller than 69905067 bytes for the ...
I keep getting this error when building our site with a newly added component using getServerSideProps. Doing netlify build locally, ...
Read more >Request must be smaller than 69905067 bytes for the ...
I'm trying to run a background function that uses lighthouse, which ultimately depends on chromium binaries. Since chromium/puppeteer is too large to bundle ......
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
This is related https://github.com/redwoodjs/redwood/issues/1345
This is probably even more related, this discussion on Discord https://discord.com/channels/679514959968993311/716252919875240007/772837339059716137 TL;DR: Switch to Vercel 🙁 Someone else said “All I had to do was rebuild without cache on netlify”
Another one: https://github.com/redwoodjs/playground-auth/pull/9
Ohh, and also this about binaryTarget: https://github.com/redwoodjs/redwoodjs.com/issues/446
@thedavidprice for sure I am looking forward to contributing. Actually got a baby PR merged in the other day. To be fair this was probably on me because this was a project that I started a while ago and picked back up. So it looks like the
binaryTargets = env("BINARY_TARGET")
in theschema.prisma
was the culprit. That is good to know. I can be update this tonative
to remove theenv
dependency. Thanks for pointing me to the docs about contributing to the docs! 😉