Environment
- Operating system:
macOS 24.6.0
- CPU:
Apple M4 (10 cores)
- Node.js version:
v24.13.0
- nuxt/cli version:
3.32.0
- Package manager:
pnpm 10.28.1
- Nuxt version:
4.3.0
- Nitro version:
2.13.1
- Builder:
vite 7.3.1
- Config:
compatibilityDate, devtools, modules, nitro
- Modules:
@nuxt/content 3.11.0, @nuxt/ui 4.4.0
Version
3.11.0
Reproduction
https://github.com/mateusznarowski/content-issue
https://content-issue.weathered-star-2306.workers.dev
Description
I am in the process of migrating from NuxtHub Admin to Cloudflare Workers directly, and I encountered an bug that prevents custom components (/components/content/) used in the content of a markdown file from rendering on the server side. On the client side, they render correctly after a while. However, if you use a component such as tip from Nuxt UI, it will be rendered correctly on the server side.
The error does not occur in dev mode or on vercel, only when building the application in the cloudflare_module preset and running it via npx wrangler --cwd .output dev or deploying it using npx wrangler --cwd .output deploy.
However, I found a pattern: if I use a given component directly in a .vue file (e.g., in app.vue), that component will be rendered correctly on the server side, but this does not affect the other components in the content.
Additional context
No response
Logs
Environment
macOS 24.6.0Apple M4 (10 cores)v24.13.03.32.0pnpm 10.28.14.3.02.13.1vite 7.3.1compatibilityDate, devtools, modules, nitro@nuxt/content 3.11.0, @nuxt/ui 4.4.0Version
3.11.0
Reproduction
https://github.com/mateusznarowski/content-issue
https://content-issue.weathered-star-2306.workers.dev
Description
I am in the process of migrating from
NuxtHub AdmintoCloudflare Workersdirectly, and I encountered an bug that prevents custom components (/components/content/) used in the content of a markdown file from rendering on the server side. On the client side, they render correctly after a while. However, if you use a component such astipfrom Nuxt UI, it will be rendered correctly on the server side.The error does not occur in
devmode or onvercel, only when building the application in thecloudflare_modulepreset and running it vianpx wrangler --cwd .output devor deploying it usingnpx wrangler --cwd .output deploy.However, I found a pattern: if I use a given component directly in a
.vuefile (e.g., inapp.vue), that component will be rendered correctly on the server side, but this does not affect the other components in the content.Additional context
No response
Logs