Nuxt Content is currently not compatible. Here are some issues I think need to be addressed:
[ ] subpath export for runtime utilities/types that are intended to be directly imported. (Currently it's documented to use @nuxt/content/dist/* - we should probably add this as a subpath at a minimum and then recommend using a more ergonomic path
[ ] emit .d.mts and .mjs (with .d.ts as legacy fallback) within runtime directory - we are currently missing the .mjs files which also leads to broken import types. I think this likely needs to be handled by default by @nuxt/module-builder
We are planning to enable
Bundlermodule resolution by default in future (see https://github.com/nuxt/nuxt/pull/22821).Nuxt Content is currently not compatible. Here are some issues I think need to be addressed:
@nuxt/content/dist/*- we should probably add this as a subpath at a minimum and then recommend using a more ergonomic path.d.mtsand.mjs(with.d.tsas legacy fallback) within runtime directory - we are currently missing the.mjsfiles which also leads to broken import types. I think this likely needs to be handled by default by@nuxt/module-builder