hybrid holly
Hey everyone 👋
I’m migrating our e‑commerce site from WordPress + WooCommerce to Astro, deployed on Cloudflare Workers.
The project is still in progress (product pages + translations missing, eventually 5 languages).
After integrating our blog (181 MDX posts) into Astro Content Collections, the Cloudflare build started failing:
✘ [ERROR] Your Worker exceeded the size limit of 3 MiB.
Please upgrade to a paid plan to deploy Workers up to 10 MiB.
Upgrading isn’t an issue, but the build already produces a 24 MB chunk
(_astro_data-layer-content.mjs), so I’m concerned it won’t scale—even with the 10 MiB limit.
Content (roughly):
- authors (3)
- blog-posts (181) – new
- kb-articles (94)
- products (385)
- category-pages (6)
- documents (123)
- faqs (26)
- single-pages (15)
- timeline (20)
- ~432 product metadata MD files in
src/data/
Everything is built statically (SSG) with getStaticPaths; locally it works perfectly, only Cloudflare fails due to the bundle size.
Setup
- Astro v5.15
- <@&1055234544183287879>/cloudflare adapter
- Astro Content Layer API
I know I could move product data to a D1 database, but even without it, the blog + KB posts (x5 languages) would likely still hit these limits.
I’m not after debugging help — just curious if this approach still fits Astro’s intended use, or if there are better patterns for handling large static content on Cloudflare.
Thanks a lot for your input! 🙏
Any real‑world experience or best practices would be super helpful ❤️
short creek