From 6a8f3eb9d1b955f0f77467d0b7d6d62f65d0401b Mon Sep 17 00:00:00 2001 From: SelfhostedPro Date: Thu, 27 Feb 2025 15:15:28 -0800 Subject: [PATCH] Update troubleshooting.mdx to include common causes of inflated build size I am all for promoting paid plans especially with such a generous free tier but including some common issues here could be beneficial. --- pages/cloudflare/troubleshooting.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/cloudflare/troubleshooting.mdx b/pages/cloudflare/troubleshooting.mdx index b0521a5..a877b9d 100644 --- a/pages/cloudflare/troubleshooting.mdx +++ b/pages/cloudflare/troubleshooting.mdx @@ -15,6 +15,10 @@ If you need to deploy to Cloudflare Pages, you can use `@cloudflare/next-on-page The Cloudflare Account you are deploying to is on the Workers Free plan, which [limits the size of each Worker to 3 MiB](https://developers.cloudflare.com/workers/platform/limits/#worker-size). When you subscribe to the Workers Paid plan, each Worker can be up to 10 MiB. +Some common underlying factors could be: +- [Metadata Icons](https://nextjs.org/docs/app/api-reference/file-conventions/metadata/app-icons) +- Assets located outside of the public directory + ### My app fails to build when I import a specific NPM package First, make sure that the `nodejs_compat` compatibility flag is enabled, and your compatibility date is set to on or after "2024-09-23", in your [wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).