How to deal with the too large submission when deploying my next.js project to Cloudflare?

[shell maple]

My Next.js project is deployed to Cloudflare, but it reports that the bundle size is too large and requires me to upgrade my plan. However, my deployment size shows only 22 MB, and even after upgrading, the limit is still 10 MB, which is not enough.

I’m sure my project isn’t very complex — it has only 12 frontend pages, all purely frontend code, with no Cloud Functions used. However, I do use internationalization (i18n).

The AI explanation says that because of i18n, each page is bundled with its own separate runtime, which increases the overall size.

How should I handle this issue and successfully deploy my project to Cloudflare?

[still galleon]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[frosty sierra]

If its all frontend with no server stuff you dont need workers at all. add output export to your next config and itll build as a static site. then deploy to cloudflare pages as static files, no worker involved so no size limit, the i18n is probably forcing it into worker mode when you dont actually need it. The static export should handle i18n fine for client side routing.

[shell maple]

Thank you for your help. After my analysis, I also think the issue is caused by internationalization. My current project needs to support two languages — are there any solutions for this? Or, if I refactor my project to support only one language, is there a minimal-change approach that would allow me to deploy to Cloudflare?

[frosty sierra]

for two languages on Cloudflare, you could use next-intl with path-based routing (/en/about, /zh/about) and set your middleware to run on edge, thats the setup that actually works without fighting Cloudflare