Repository navigation
|
I've run into an issue where I can either deploy a page (typical size It seems as if these two lambdas contribute toward the same file size quota. Can anyone confirm if that's true? I had thought that dependencies/static assets were split across lambdas and that they all had some theoretical maximum footprint. If there is a collective limit, is that limit the same across all Zeit pricing tiers? It's worth noting here that my API contains FWIW these are my deploy logs: |
Replies: 8 comments 9 replies
|
Does anyone have any idea how to manually shrink a lambda? I've tried restricting dependencies on a function-by-function basis but it doesn't seem to have an effect. Any idea what I'm going wrong? from |
|
Are you able to create a minimal reproducible example? |
|
Hi @styfle + @paulogdm just ran into a similar issue! I created a new API endpoint that used the same dependency as my original page (in this case Is that intended behavior? Does each API become its own discrete lambda (or do all pages get pooled together for a I've updated my example repo to demonstrate, |
|
To be clear, the issue I'm having now: is in order for my app to deploy I need to delete either:
Either of those will deploy if the other has been removed. As with the issue I was having before, it seems like all dependencies for all API endpoints are being bundled together versus being intelligently split up per lambda. Any help would be greatly appreciated! |
|
Any thoughts on what might be causing this @paulogdm? Should I re-post this as a new thread? |
|
@sambecker I created a PR to your repo here: sambecker/now-function-size#11 cc @marklawlor who had a similar problem |
Thanks for the repo!
This will be fixed in PR #4018.
Also, please update to the latest Next.js version to ensure the latest bug fixes.