Hi, awesome people 👋 Having a weird issue with deploying Lambda@Edge functions using

aws.lambda.CallbackFunction

. For some reason, Pulumi started deploying these functions included a big portion of

node_modules

in the package, which deploys a package size of +15.5 MB (which is too big to use as a Lambda Edge. I have tried stripping everything in the function and making sure to prevent any open closures, basically reducing it to

callback: () => {}

. No matter what I do, it keeps including

node_modules

in the lambda package itself. It used to worked perfectly, now I have zero idea what I suddenly did wrong to trigger this. Any ideas how I can debug this, or how I can force-exclude

node_modules

from the package?

Do you know what version of the pulumi sdk this used to work with?

Ah, you're saying something. I think I just upgraded. Is there a know breaking change regarding this?

I don't know of any, and looking at the nodejs repo I can't see anything obvious in history but I'm not the resident nodejs expert 🙂 If you do have a version it worked at that will help narrow it down (and also confirm it is due to an sdk change and not some other dependency changing)

I will try this and get back, thanks.

No luck using old SDK versions?

Unfortunately, no luck with earlier versions, no.

Unfortunately, no luck with earlier versions, no.

Shame that would of made things easier

Do you know of any way I can customize the serialization process?

I don't, it's all black magic to me 😆 I'd suggest raising an issue at our github, can get one of the more "nodejs knowledgeable" team members to have a look.

That would be great. I see the "black magic" is actually very well-described here - except, it doesn't do what it says it does here 😅 It exactly doesn't strip the

node_modules

, and it doesn't seem like there's any way to add custom logic to this process 😞 https://www.pulumi.com/docs/intro/concepts/function-serialization/