Hi @rotund pike. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Issues with Docs md
pastel creekBOT
Nuxt Content changes in Markdown files should normally be picked up by HMR and reflected immediately in dev, so there isn’t a special “docs” setting you need to turn on. The behavior you describe sounds like an HMR / caching issue rather than a docs-setup problem.
From the available sources, there are a few relevant HMR notes but nothing specific to Markdown-in-content/ not updating in dev. There is a known general HMR flakiness on some setups (especially Windows) where changes don’t reliably trigger a reload, and the Nuxt docs now recommend using WSL on Windows for much faster and more reliable HMR when developing there.[HMR note]
Beyond that, the knowledge sources don’t give concrete troubleshooting steps for your exact case (Markdown in content/ under a dynamic pages/docs/[slug].vue route). I don’t have more specific, documented checks (like particular nuxt.config flags, dev server options, or @nuxt/content-specific caveats) in these sources.
Given that, all I can confidently suggest from the docs you’ve provided is:
- If you’re on Windows and not using WSL, try running your Nuxt dev server inside WSL (e.g. Ubuntu on WSL), as that’s explicitly recommended for reliable HMR.[HMR note]
- If you’re already doing that or on another OS, the knowledge sources don’t contain further Nuxt-Content-specific HMR guidance, so I can’t point you to a documented fix.
If you can share your OS, Nuxt version, and how you’re running dev (and whether you’re on Windows/WSL), the next step would be to check the official Nuxt or Nuxt Content docs / issues directly, since that level of detail isn’t present in the sources here.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
rotund pike
It worked before.