content: [Vue warn]: Failed to resolve component: MDCRenderer when upgrading to Nuxt 3.8.2
Environment
Nuxt project info: 19:20:01
- Operating System: Windows_NT
- Node Version: v20.7.0
- Nuxt Version: 3.8.2
- CLI Version: 3.10.0
- Nitro Version: 2.7.2
- Package Manager: yarn@4.0.2
- Builder: -
- User Config: extends, devtools, dev, debug, modules, typescript, ssr, routeRules, nitro, linkChecker, css, runtimeConfig, app, build, nuxtIcon, vueuse, content, experimental
- Runtime Modules: @unocss/nuxt, @nuxt/content, @vueuse/nuxt@10.6.1, nuxt-icon, @nuxtjs/mdc
- Build Modules: -
π Report an issue: https://github.com/nuxt/nuxt/issues/new 19:20:01
π Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new
π Read documentation: https://nuxt.com
Reproduction
This is my content config, that has not changed for a long time
content: {
documentDriven: false,
highlight: {
// Theme used in all color schemes.
theme: "github-light",
preload: [
"diff",
"ts",
"ini",
"docker",
"js",
"css",
"java",
"groovy",
"markdown",
"sql",
"xml",
"json"
]
},
markdown: {
mdc: true,
toc: {
depth: 4,
searchDepth: 4
}
}
},
```
and I'm using the ContentRenderer like this
```
<ContentRenderer :value="post"/>
```
### Describe the bug
I'm suddenly getting
```
[Vue warn]: Failed to resolve component: MDCRenderer
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
[Vue warn]: Component <Anonymous> is missing template or render function.
```
for my application.
I've dropped in `@nuxtjs/mdc` in hope it would resolve the missing component, but seems to be not related.
### Additional context
_No response_
### Logs
_No response_
About this issue
- Original URL
- State: open
- Created 7 months ago
- Reactions: 8
- Comments: 19 (2 by maintainers)
Commits related to this issue
- fix: downgrading the version because of problems with the new version of nuxt see https://github.com/nuxt/content/issues/2443 — committed to elonehoo/elonehoo.me by elonehoo 7 months ago
I just ran
npx nuxi upgrade(remove node_modules and yarn.lock). And it works π€·ββοΈ.My deps
Iβm having the same problem. This works
So does this
But this wonβt
I am having the same issue