don't do this
`
import { z } from 'zod'
`
In the content.config.ts, the issue it seems like the `asSeoCollection` from the #NuxtSeo module won't create the types for some reason.
don't do this
`
import { z } from 'zod'
`
In the content.config.ts, the issue it seems like the `asSeoCollection` from the #NuxtSeo module won't create the types for some reason.
This is an experiment with the @nuxtlabs.com #nuxtcontent V3 , is early and some modules for SEO are not there yet so
manual steps need to be taken.
#buildinpublic #vue #nuxt #nuxtseo
This is an experiment with the @nuxtlabs.com #nuxtcontent V3 , is early and some modules for SEO are not there yet so
manual steps need to be taken.
#buildinpublic #vue #nuxt #nuxtseo
So created step to make it for me, the build bundle. #nuxt #vue #coolify #nuxtcontent
So created step to make it for me, the build bundle. #nuxt #vue #coolify #nuxtcontent
don't do this
`
import { z } from 'zod'
`
In the content.config.ts, the issue it seems like the `asSeoCollection` from the #NuxtSeo module won't create the types for some reason.
don't do this
`
import { z } from 'zod'
`
In the content.config.ts, the issue it seems like the `asSeoCollection` from the #NuxtSeo module won't create the types for some reason.
✨ 6 modules: Robots, Sitemap, OG image, Schema․org, Link checker, plus SEO Utils.
🔨 2 years of improvements: 884 issues closed & 4.8K commits.
🧑🎨 Brand new docs.
nuxtseo.com/announcement
it's not the _import_ that gets overridden, though.
rather, Nuxt merges your `nuxt.options` from all your layers. so if one of your layers sets one property, but the final project that uses the layer sets the property to something different, it will override it.
it's not the _import_ that gets overridden, though.
rather, Nuxt merges your `nuxt.options` from all your layers. so if one of your layers sets one property, but the final project that uses the layer sets the property to something different, it will override it.