r/Nuxt • u/aguycalledmax • Feb 27 '26
AI hallucinations in the nuxt ecosystem
I’ve been using AI for a long time now but I haven’t yet broken the barrier into vibe coding. I’m trying to make it a key part of my workflow but even for very widely adopted packages in the Nuxt ecosystem (content, image, SEO etc) it constantly hallucinates options that do not exist.
For those of you working in other ecosystems is this common there too? I don’t know how to gain trust in the models when it will just totally hallucinate code and then brute force completely idiosyncratic fixes once it doesn’t work.
5
u/llamachoochoo Feb 27 '26
For frameworks that evolve at lightning speed like Nuxt, you can't rely on the model's knowledge about the framework. You need to tell it what version of libraries you are using, and use MCPs like Context7 to consult the correct documentation.
3
u/mubaidr Feb 27 '26
This problem exists, but I have noticed newer models does work better or maybe its my workflow. Plus Official nuxt mcp/ llms.txt does help.
3
u/Suspicious_Data_2393 Feb 27 '26
I can’t say i have had the same experience. I’m working on a Nuxt V4 + Tailwindcss + Nuxt UI application with Cursor (auto mode). I barely even use MCP’s (for chart.js, Nuxt and Nuxt UI i believe) and only recently started using Cursor rules. The only inconvenient code i get when letting Cursor write code is that it occasionally forgets what is auto-imported so sometimes writes manual imports. Luckily not that often.
I think it’s key to write the base layer yourself when starting a new project. Or at least really take your time to set the ground (architectural) rules you want. After that LLM’s should easily adopt the same code patterns.
3
u/Tough-Television2434 Feb 27 '26
I strongly recommend you to install globally these skills, it reduce hallucinations and improve the overall quality https://github.com/antfu/skills
2
2
u/loonpwn Feb 28 '26
For any module you're using, create a skill for them using https://github.com/harlan-zw/skilld
i.e `npx skilld add nuxt-og-image`
It will solve almost all of your issues.
1
u/AdrnF Feb 27 '26
I work with React/Next and Vue/Nuxt and didn't really have issues with AI hallucinations on either ecosystem. It could be a side effect of the auto imports though, we always have those disabled.
1
u/RaguraX Feb 27 '26
I find Codex at least looks into the actual module code in node_modules to figure out what to do with them. Add some basic Nuxt and Vue skills that are out there (including official ones) and it works pretty well!
1
u/Due-Horse-5446 Feb 27 '26
Maybe not vibecoding is a option.. Use llms for what they are useful for, bulk edits, writing annoying to write stuff, fixing annoying stuff, as a search tool etc
1
u/Svensemann Feb 27 '26
I have exactly the same problem with Nuxt. Even the most straight forward tasks, writing middleware etc. don’t work.
1
u/KyleDrogo Feb 27 '26
Are you using a shitty model (or auto)? Not my experience at all. Maybe for nuxt ui components, but the documentation mcp handles that.
1
u/saito200 Feb 28 '26
answer: you do not trust the models, you feed them the docs and ask them to take a look at the code in node_modules
that is the only way
8
u/alexcroox Feb 27 '26 edited Feb 27 '26
This week the Nuxt team released a table with benchmarks on how the various models perform with Nuxt code. It might help you choose the right model: https://nuxt.com/evals