I ran into a prerender crash in a Docus docs app when the dependency graph ended up with mixed h3 versions:
- Nuxt/Nitro runtime on
h3@1.15.11
docus -> @nuxtjs/mcp-toolkit resolved against h3@2.0.1-rc.20
In that setup, prerender could crash with:
TypeError: event.req.headers.entries is not a function
setResponseHeader(... reading 'set')
This does not look like a general @nuxt/content problem. It seems specific to the Docus docs stack ending up with h3 v1 and v2 in the same app.
What worked for me was making sure the docs app resolves back to the normal Nuxt/Nitro h3@1 path.
Reference PR with the workaround and verification:
cc @HugoRCD
I ran into a prerender crash in a Docus docs app when the dependency graph ended up with mixed
h3versions:h3@1.15.11docus -> @nuxtjs/mcp-toolkitresolved againsth3@2.0.1-rc.20In that setup, prerender could crash with:
TypeError: event.req.headers.entries is not a function setResponseHeader(... reading 'set')This does not look like a general
@nuxt/contentproblem. It seems specific to the Docus docs stack ending up withh3v1 and v2 in the same app.What worked for me was making sure the docs app resolves back to the normal Nuxt/Nitro
h3@1path.Reference PR with the workaround and verification:
cc @HugoRCD