null is not an object (evaluating 'instance.__vrv_devtools = info')
getting a weird error after JS is injected into the page.
null is not an object (evaluating 'instance.__vrv_devtools = info')
even on a page that has nothing except <template>. this is with a vite server.
2 Replies
Hi @pinefin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
This error looks related to Nuxt DevTools / Vue DevTools integration in a Vite dev server, but the provided knowledge sources do not mention
If you’re on a very recent Nuxt 4 + Vite 6 combo, you might be hitting an edge bug; if you’re on an older combo, upgrading may help. 3. Check for dev‑only routing / middleware edge cases. Other dev‑only errors were caused by catch‑all routes intercepting internal dev files (e.g. service workers) and then failing in the dev error overlay.[html.replace workaround]
If you have a
__vrv_devtools or this exact error string at all, so I can’t give a definitive cause.
From what we do have:
- There are known dev‑time errors coming from devtools / Vite integration in recent Nuxt 4 versions (e.g. html.replace is not a function and blank pages) that only happen with SSR enabled and/or certain routes, and they’re tied to devtools and Vite regressions rather than to user code.[html.replace issue][rolldown-vite issue]
- Nuxt DevTools exposes composables like useNuxtDevTools and host‑client helpers, which are only initialized when DevTools is active; they are undefined/null otherwise.[Devtools composable][host-client utils]
Given that, the safest, evidence‑based suggestions I can make are:
1. Temporarily disable Nuxt DevTools in your Nuxt config and see if the error disappears. (The docs confirm DevTools can be disabled, but the exact config key is not shown in the snippets above, so I can’t quote it directly.) If disabling DevTools removes the error, it’s very likely a DevTools/runtime mismatch.
2. Confirm your Nuxt and Vite versions. There are active changes around Vite 6 and devtools integration (for example, Nuxt updating to Vite 6.3.5 and @nuxt/devtools v3 with new “Vite DevTools” support).[Vite 6.3.5 PR][Devtools v3 PR]If you’re on a very recent Nuxt 4 + Vite 6 combo, you might be hitting an edge bug; if you’re on an older combo, upgrading may help. 3. Check for dev‑only routing / middleware edge cases. Other dev‑only errors were caused by catch‑all routes intercepting internal dev files (e.g. service workers) and then failing in the dev error overlay.[html.replace workaround]
If you have a
pages/[...slug].vue or similar, try temporarily removing it or adding Nitro middleware to block requests to internal dev paths to see if the error changes.
Because the sources don’t reference __vrv_devtools at all, I can’t say more without guessing. If you can share:
- Your nuxt and vite versions,
- Whether Nuxt DevTools is enabled,
- And whether the error persists with DevTools disabled,
then you could open a Nuxt issue, referencing that it’s a devtools/Vite error similar in spirit to the existing dev‑time issues above, and include a minimal repro.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@918151599807946752> Kapa.ai is still learning and improving, please let me know how I did by reacting below.