Next 11 Serverless Functions Break - "Request be smaller than 69905067 bytes for the CreateFunction Operation"

[NoahBres]

Describe the bug
I have a very small serverless function, 114 lines long with 2 relatively small packages, and it kills the netlify deploys after upgrading to Next 11. It was working fine on Next 10.

The function compiles to 63.9kb according to next build.

However, upon deploy, this function throws the error "Request must be smaller than 69905067 bytes for the CreateFunction operation." This error seems to be related to AWS lambda functions setting a package size limit of 50mb. This function is definitely under that.

To Reproduce

1. Implement serverless function
   • Found here:
     vishnuSriram/operation-medical-care@7e5a668#diff-bfa062de040f55a15ce910800757061ec3d2fc31d6b7c72d9fa02b75a9ad1133
2. Deploy build

Versions

• Next.js: 11.0.0

Here is our deploy log if helpful: https://gist.github.com/vishnuSriram/270e0a5a72122a91c1494fd4a6544524

[lindsaylevine]

@NoahBres hey noah! so sorry you're running into this!

do you have esbuild configured in your netlify.toml? (see docs https://docs.netlify.com/configure-builds/file-based-configuration/#functions). this should resolve your problem. let us know if it does!

note: esbuild in its current state breaks dynamic imports in next. if you're using dynamic imports in your site, we have a fix for the broken imports behind a feature flag. to enable it, add NETLIFY_EXPERIMENTAL_PROCESS_DYNAMIC_IMPORTS as an environment variable with the value set to true. if you do set this up and test it out, please let us know too! feedback would be invaluable!!!

[NoahBres]

This worked great! Thank you so much!!

I did not have dynamic imports so can't give any feedback on that. But thank you for this fix!

[tgmarinho]

@NoahBres hey noah! so sorry you're running into this!

do you have esbuild configured in your netlify.toml? (see docs https://docs.netlify.com/configure-builds/file-based-configuration/#functions). this should resolve your problem. let us know if it does!

note: esbuild in its current state breaks dynamic imports in next. if you're using dynamic imports in your site, we have a fix for the broken imports behind a feature flag. to enable it, add NETLIFY_EXPERIMENTAL_PROCESS_DYNAMIC_IMPORTS as an environment variable with the value set to true. if you do set this up and test it out, please let us know too! feedback would be invaluable!!!

it's working for me also, thanks!

[tgmarinho]

Complete solution here: #571 (comment)

[Gnarus-G]

I am currently wrestling with this issue.

I've applied these configurations as I've read to do.

Am I missing something?

P.S. Here is the source code if you need it, https://github.com/Gnarus-G/bytin

[lindsaylevine]

@Gnarus-G just to confirm - you're getting the "request must be smaller than.." error?

[Gnarus-G]

@lindsaylevine Yes I am.

[lindsaylevine]

@Gnarus-G gotcha, okay. would you be willing to give our plugin rewrite alpha a try? it's not ready for production, but i predict it will fix your issue. a formal beta will be released at the end of this week. to try, install https://www.npmjs.com/package/@netlify/plugin-nextjs-experimental and follow the instructions there. let us know!

[Gnarus-G]

@lindsaylevine Still getting the issue.

[lindsaylevine]

i think you can remove esbuild and external_node_modules (not sure about all but you definitely shouldnt need next in there). i'd give that a try.

[Gnarus-G]

@lindsaylevine Thanks very much for your help.

I removed esbuild and external_node_modules configs, and it finally deployed. I'm happy about that.
But now there's an

on my /api route which should show a Graphiql interface.

But I don't care anymore, my production is working fine on vercel so I'm good. You can ignore me now.