| Property was accessed during render but is not defined |
Vue: [Vue warn]: Property "x" was accessed during render but is not defined on instance |
The template references a variable/function that the component doesn’t expose. |
| Failed to resolve component |
Vue: [Vue warn]: Failed to resolve component: x |
The template uses a component tag that isn’t registered or imported where it’s used. |
| getActivePinia() was called but there was no active Pinia |
Pinia: Error: [🍍]: "getActivePinia()" was called but there was no active Pinia. Are you trying to use a store before calling "app.use(pinia)"? |
A store was used before Pinia was installed or outside a component context (router guards, plain modules). |
| v-else/v-else-if has no adjacent v-if |
Vue: [plugin:vite:vue] v-else/v-else-if has no adjacent v-if or v-else-if. |
A `v-else` element isn't directly after a `v-if`/`v-else-if` sibling. |
| Nuxt: window/document/localStorage is not defined (SSR) |
Nuxt: ReferenceError: window is not defined / 500 Internal Server Error during SSR |
Code touching browser globals ran on the server during Nuxt SSR. |
| injection "Symbol(router)" not found / useRouter() called without router |
Vue Router: [Vue warn]: injection "Symbol(router)" not found. / Cannot read properties of undefined (reading 'push') |
`useRouter()`/`useRoute()` ran in a component tree where the router plugin isn't installed. |
| Avoid mutating a prop directly |
Vue: [Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders |
A child component assigned to a prop. Props flow one way — the parent owns the value. |
| [Vue warn]: Component is missing template or render function |
Vue: [Vue warn]: Component is missing template or render function. |
A component object has neither `template` nor `render`, or an SFC import resolved wrongly. |
| [Vue warn]: Extraneous non-props attributes |
Vue: [Vue warn]: Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text root nodes |
Attributes (class, style, listeners) passed to a component can't be applied because the component has multipl… |
| [Vue warn]: Failed to locate Teleport target with selector |
Vue: [Vue warn]: Failed to locate Teleport target with selector "#modal". Note the target element must exist before the component is mounted |
`` can't find its target element when mounting. |
| [Vue warn]: Maximum recursive updates exceeded |
Vue: [Vue warn]: Maximum recursive updates exceeded in component <Foo>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself |
A watcher/computed/render effect keeps changing the state it depends on, creating an infinite update loop. |
| [Vue warn]: Set operation on key failed: target is readonly |
Vue: [Vue warn]: Set operation on key "name" failed: target is readonly. |
You mutated a readonly reactive object (props, `readonly()`, `shallowReadonly`, or a frozen/store state). |
| 404 on page refresh (history mode) |
Browser: Cannot GET /users/42 — refreshing a Vue Router history-mode page returns 404 |
In history mode the server must serve `index.html` for all routes; otherwise direct URLs/refreshes hit non-ex… |
| Component provided template option but runtime compilation is not supported |
Vue: [Vue warn]: Component provided template option but runtime compilation is not supported in this build of Vue. Configure your bundler to alias "vue" to "vue/dist/vue.esm-bundler.js" |
A component uses a string `template` but the runtime-only Vue build has no compiler. |
| Error: [vuex] do not mutate vuex store state outside mutation handlers |
Vuex (strict mode): Error: [vuex] do not mutate vuex store state outside mutation handlers. |
Store state was modified directly (in a component or action) while strict mode is on. |
| vue/multi-word-component-names |
ESLint: error Component name "Home" should always be multi-word vue/multi-word-component-names |
ESLint's Vue rules require component names with at least two words to avoid clashing with HTML elements. |
| ESLint Parsing error in .vue files |
ESLint: Parsing error: Unexpected token < / Parsing error: '>' expected (vue-eslint-parser not configured) |
ESLint can't parse `.vue` files because the Vue parser isn't configured. |
| useAsyncData/useFetch must be called in setup (key/context) |
Nuxt: [nuxt] [useAsyncData] key must be a string / useFetch only works inside setup, plugins or middleware |
`useFetch`/`useAsyncData` were used in an event handler, after an await, or without a key where one is requir… |
| Nuxt: Failed to fetch dynamically imported module (after deploy) |
Nuxt: [nuxt] error caught during app initialization TypeError: Failed to fetch dynamically imported module / Loading chunk failed |
A browser tab running the old build requests chunk files that were replaced by a new deployment. |
| Nuxt/Vite: Failed to resolve import "~/..." or "@/..." |
Nuxt: [vite] Internal server error: Failed to resolve import "~/components/Foo.vue" from "pages/index.vue". Does the file exist? |
Vite couldn't resolve an alias import — the file doesn't exist at that path or the alias isn't defined. |
| Nuxt: Hydration completed but contained mismatches |
Nuxt: [Vue warn]: Hydration completed but contains mismatches. |
Server HTML and client render differed; Vue patched the DOM but logs the mismatch. |
| Nuxt 404: Page not found (route/file naming) |
Nuxt: 404 Page not found: /blog/my-post / [Vue Router warn]: No match found for location with path |
Nuxt's file-based router has no page matching the URL (wrong file/folder names or missing param syntax). |
| [Vue Router warn]: No match found for location with path |
Vue Router: [Vue Router warn]: No match found for location with path "/users/42" |
The router has no route record matching that path (typo, missing route, or case/base issue). |
| Element is missing end tag |
Vue: [plugin:vite:vue] Element is missing end tag. / Invalid end tag. |
The template has unbalanced HTML tags. |
| [Vue warn]: <TransitionGroup> children must be keyed |
Vue: [Vue warn]: <TransitionGroup> children must be keyed: <li> |
Children of `` lack a unique `key`, so animations can't track items. |
| [Vue warn]: Component emitted event but it is neither declared in the emits option nor as an onXxx prop |
Vue: [Vue warn]: Component emitted event "update" but it is neither declared in the emits option nor as an "onUpdate" prop |
A component calls `emit("update")` without declaring it in `emits`. |
| [Vue warn]: Duplicate keys found during update |
Vue: [Vue warn]: Duplicate keys found during update: "5", possible duplicate or missing keys |
Items in a `v-for` list share the same `:key`, which breaks Vue's diffing. |
| [Vue warn]: injection "x" not found |
Vue: [Vue warn]: injection "theme" not found. |
`inject("theme")` ran but no ancestor provided it. |
| [Vue warn]: Missing required prop |
Vue: [Vue warn]: Missing required prop: "title" |
A component marked a prop as `required` but the parent didn't pass it. |
| Tags with side effect (<script>/<style>) are ignored in client component templates |
Vue: [Vue warn]: Template compilation error: Tags with side effect (<script> and <style>) are ignored in client component templates |
A component template contains ``/`` tags, which Vue won't render. |
| [Vue warn]: The computed property "x" is already defined in data/props |
Vue: [Vue warn]: The computed property "name" is already defined in data. |
A name is used twice among props/data/computed/methods in the Options API. |
| [Vue warn]: Unhandled error during execution of setup/mounted hook |
Vue: [Vue warn]: Unhandled error during execution of mounted hook / TypeError: Cannot read properties of undefined (reading 'x') |
An exception was thrown inside a lifecycle hook, watcher, event handler or render, and Vue logs it with the c… |
| v-if with v-for on the same element |
Vue: [vue/no-use-v-if-with-v-for] / Vue 3: v-if has higher priority than v-for — property accessed during render is undefined |
Using `v-if` and `v-for` on one element: in Vue 3, `v-if` runs first and can't see the loop variable. |
| Feature flags __VUE_OPTIONS_API__ not explicitly defined (esm-bundler) |
Vue: You are running the esm-bundler build of Vue — configure your bundler to explicitly replace feature flag globals (__VUE_OPTIONS_API__) |
A bundler build of Vue 3 lacks the feature-flag defines (`__VUE_OPTIONS_API__`, `__VUE_PROD_DEVTOOLS__`, `__V… |
| Cannot find module './App.vue' or its corresponding type declarations |
TypeScript: error TS2307: Cannot find module './App.vue' or its corresponding type declarations. |
TypeScript doesn't know what a `.vue` import is without a shim or Volar/`vue-tsc`. |
| Vite: Failed to parse source / Unknown file extension ".vue" |
Vite/Vue: [plugin:vite:import-analysis] Failed to parse source for import analysis — you may need to install appropriate plugins to handle the .vue file format |
Vite can't process `.vue` files because the Vue plugin isn't installed/enabled. |
| [Vue warn]: Avoid adding reactive properties to a Vue instance or its root $data at runtime |
Vue 2: [Vue warn]: Avoid adding reactive properties to a Vue instance or its root $data at runtime - declare it upfront in the data option |
In Vue 2 you added a property to the root data (or instance) after creation, which can't be made reactive. |
| [Vue warn]: Error in v-on handler / Error in mounted hook (Vue 2) |
Vue 2: [Vue warn]: Error in v-on handler: "TypeError: Cannot read property 'x' of undefined" |
An exception was thrown inside a Vue 2 event handler or lifecycle hook, logged with context. |
| next() called multiple times in navigation guard |
Vue Router: [Vue Router warn]: The "next" callback was called more than once in one navigation guard when going from "/a" to "/b" |
A navigation guard called `next()` more than once, which breaks navigation. |
| v-model cannot be used on a prop (compile error) |
Vue: [@vue/compiler-sfc] v-model cannot be used on a prop, because local prop bindings are not writable |
A template uses `v-model` on a prop (or a `v-for` alias), which can't be assigned. |
| Duplicate attribute (Vue template) |
Vue: [plugin:vite:vue] Duplicate attribute. / [vue/no-duplicate-attributes] Duplicate attribute 'class' |
The same attribute appears twice on an element in a template. |
| [Vue warn]: Hydration node/text/children mismatch |
Vue: [Vue warn]: Hydration text content mismatch / Hydration node mismatch: server rendered element contains more child nodes than client vdom |
Server-rendered HTML differs from what the client renders on first load. |
| [Vue warn]: Slot "default" invoked outside of the render function |
Vue: [Vue warn]: Slot "default" invoked outside of the render function: this will not track dependencies used in the slot |
A slot function was called outside render (in `setup`, a computed or watcher), so reactivity isn't tracked. |
| this.$refs.x / ref.value is undefined or null before mount |
Vue: TypeError: Cannot read properties of undefined (reading 'focus') — template ref accessed before the component is mounted |
A template ref (`ref="input"`) is read before the element exists (setup, created, or before `v-if` renders it… |
| Failed to fetch dynamically imported module / async component failed |
Vue: TypeError: Failed to fetch dynamically imported module: https://app.example.com/assets/Settings-abc123.js |
A lazy-loaded route/component chunk couldn't be loaded (new deployment removed old chunks, network issue, or… |
| [vuex] unknown mutation type / unknown action type |
Vuex: [vuex] unknown mutation type: SET_USER / [vuex] unknown action type: fetchUser |
`commit`/`dispatch` was called with a name that isn't registered in the store (or its module namespace). |
| vue-loader was used without the corresponding plugin |
Webpack: Error: [vue-loader] vue-loader was used without the corresponding plugin. Make sure to include VueLoaderPlugin in your webpack config. |
Webpack config uses `vue-loader` but doesn't add its plugin. |
| NavigationDuplicated: Avoided redundant navigation to current location |
Vue Router: Uncaught (in promise) NavigationDuplicated: Avoided redundant navigation to current location: "/home" |
`router.push` to the route you're already on, rejecting the promise (Vue Router 3.1+). |
| [Vue warn]: Invalid prop: type check failed |
Vue: [Vue warn]: Invalid prop: type check failed for prop "count". Expected Number with value 5, got String with value "5" |
A prop received a value of the wrong type. |
| Vue received a Component that was made a reactive object |
Vue: [Vue warn]: Vue received a Component that was made a reactive object — mark it with `markRaw` or use `shallowRef` |
A component definition was stored in a `ref`/`reactive`, making Vue proxy it unnecessarily. |
| [Vue warn]: Write operation failed: computed value is readonly |
Vue: [Vue warn]: Write operation failed: computed value is readonly |
You assigned to a `computed` that has no setter. |
| [Vue warn]: onMounted is called when there is no active component instance |
Vue: [Vue warn]: onMounted is called when there is no active component instance to be associated with |
A lifecycle hook was registered outside `setup()` (or after an `await`). |