Open mklueh opened 9 months ago
I am having the same issue
@shershen08 glad to hear I'm not the only one
it worked OK for me before I tried adding @nuxt/ui
module 2h ago...
it seems some deps has been updated during this install
@mklueh I managed to fix it by setting the exact the versions of the following pkgs:
"@nuxt-themes/docus": "1.15.0",
"@nuxt/content": "2.8.0",
especially check @nuxt/content - 2.8.0
, is 1 minor below latest which is 2.9.0
@shershen08 I'm neither using the docus theme, nor nuxt ui, but I got it working with nuxt/content:2.9.0 by downgrading some other packages đ will look into it more tomorrow
Edit: it happens as soon as I raise those Nuxt version numbers from 3.8.1 to 3.8.2
I'm having the same problem. This works
"@nuxt/content": "2.8.5",
"nuxt": "^3.8.2"
So does this
"@nuxt/content": "2.9.0",
"nuxt": "^3.8.1"
But this won't
"@nuxt/content": "2.9.0",
"nuxt": "^3.8.2"
Same issue here
I've resolved it somehow and it works with
"@nuxt/content": "2.9.0",
"nuxt": "^3.8.2"
I had the suspicion, that
import { transformerVariantGroup } from "unocss";
was responsible, so I removed it and it resolved it "somehow" in my reproducer project.
But then the issue appeared again and then I've upgraded
nuxt-seo-kit
and replaced it with the new version @nuxtseo/module
https://nuxtseo.com/nuxt-seo/getting-started/installation
Pls check if you have those packages in place
Having same issue, here is my package.json
(after downgrading to v3.8.1):
However, this did not help.
I reverted all changes to
package.json
and package-lock.json
, and it still does not work. No clue why...
)
Could you try upgrading to latest version of Nuxt and Content module with clean install? (update versions, remove your lock file and then install deps)
I just ran npx nuxi upgrade
(remove node_modules and yarn.lock).
And it works đ¤ˇââď¸.
My deps
This is a common issue with lets say all package manager that creates conflict between different versions of packages. As for this issue, different versions of scule
package might exists in your lock file and it caused this propblem.
I just ran
npx nuxi upgrade
(remove node_modules and yarn.lock). And it works đ¤ˇââď¸.My deps
not working
i am having the same issue just initialized a project and getting this error after running development server
same issue
Same issue, did everything above, not helping.
Made a blank code-sandbox with only Nuxt 3.9.0 and MDC 0.3.0 and it still does not resolve the component.
In Nuxt content documentation,
Components that are used in Markdown has to be marked as global in your Nuxt app if you don't use the components/content/ directory.
I use Nuxt ^3.9.3
and Nuxt content ^2.11.0
If I create component ~/components/content/Card.vue
component not detected,
If I create component ~/components/content/Card.global.vue
component still not detected,
And I update nuxt configuration
export default defineNuxtConfig({
components: {
global: true,
dirs: ['~/components']
},
})
Component detected in my markdown content file. I hope problem solved in you all too.
@farnabaz haven't seen this issue in a while. I'm using nuxt 3.11.1 and /content 2.12.1 now and everything work as intended.
Issue can probably be closed
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
Environment
Nuxt project info: 19:20:01
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
and I'm using the ContentRenderer like this
Describe the bug
I'm suddenly getting
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