local .next/cache folder is ~90mb, when built on vercel it's > 350mb - and I can't build

[jooles]

Summary

Hi there,
I don't know what happens, but I'm just building a basic nextjs with mui (including some icons) and some additional libs.
When building the app locally the .next/cache folder (specifically webpack) is reasonably small.
however, when doing a vercel --prod each serverless function exceeds 250mb - and I don't know why or how I'd be able to "debug".

Anyone experiencing the same or having some tips?

Thank you!
Best,
jooles

Additional information

you can find the next.config.js here:
https://pastebin.com/JkygtmJe

and the package.json here:
https://pastebin.com/6D13Dt0D

Thanks for any help!

Example

No response

[sahils0]

Try deleting the unused mui components or the unused library which you've installed earlier

[jooles]

thank you!

What unused library do you mean?

And what I'm wondering: Why is it locally significantly (!) smaller than directly on Vercel?

[jooles]

I found a solution by utilizing "outputFileTracingExcludes" - hope it stays like this.

Thanks!

[icyJoseph]

Yes, ah you beat me to it. This used to be a problem for GetServerSideProps too, which would have a very slow start, because, some UI libraries, would be part of the shared bundle. Good job!

• API routes and getServerSideProps timeout on production (Vercel) #47237 (comment)

[jooles]

Ahh.. wow. Thanks for replying though! Didn't see that thread before. What a mess.. and glad to hear, that you also found a solution to this!

[cloddo]

Can you please share more details about your solution with "outputFileTracingExcludes"? Thanks!