Error map
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?
Vue · layer 1, On your device
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
[vite] Internal server error: Failed to resolve import "x" from "src/App.jsx". Does the file exist?
Vite couldn’t find an imported file or package.
[vite] hmr invalidate … Could not Fast Refresh. Export is incompatible.
Fast Refresh fell back to a full reload because the file exports non-components alongside components.
Next.js: Module not found: Can't resolve '@/components/Button' / 'lodash' in '/app/src'
Webpack/Turbopack couldn't resolve an import — wrong path/alias, missing dependency or case mismatch.
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.
Nuxt: ReferenceError: window is not defined / 500 Internal Server Error during SSR
Code touching browser globals ran on the server during Nuxt SSR.
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).
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.
Nuxt: [Vue warn]: Hydration completed but contains mismatches.
Server HTML and client render differed; Vue patched the DOM but logs the mismatch.
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 required.
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: 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 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.
Two steps away (32)
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
Warning: A component is changing an uncontrolled input to be controlled
An input’s `value` started as `undefined` (uncontrolled) and later became a defined value (controlled), or vice versa.
TS2307: Cannot find module 'x' or its corresponding type declarations.
TypeScript can’t resolve the import — the package isn’t installed, the path alias isn’t configured, or there are no types.
Adjacent JSX elements must be wrapped in an enclosing tag. Did you want a JSX fragment <>...</>?
A component returns two sibling JSX elements without a single parent.
Warning: Cannot update a component (`Parent`) while rendering a different component (`Child`)
A child component updated a parent’s state during its render instead of in an effect or event handler.
Error: createRoot(...): Target container is not a DOM element.
The element passed to createRoot/render doesn’t exist when the script runs.
TypeError: x is not a function
You called something as a function, but its value is not a function (it’s undefined, a string, an object…).
TypeError: x is not a constructor
new was used with something that isn’t a class/constructor — usually a wrong import.
ReferenceError: Cannot access 'x' before initialization
A let/const/class was used before its declaration line ran (temporal dead zone) — often a circular import.
Vue: [Vue warn]: Failed to resolve component: x
The template uses a component tag that isn’t registered or imported where it’s used.
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: [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).
Error: Hydration failed because the initial UI does not match what was rendered on the server
The HTML rendered on the server differs from the first client render, so React (Next.js/Remix) can’t attach to it.
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>.
The JSX produces invalid HTML nesting, which also causes hydration mismatches in SSR.
Warning: useLayoutEffect does nothing on the server
A component using useLayoutEffect was server-rendered, where layout effects can’t run.
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).
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 multiple root nodes.
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: [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.
Warning: Prop `className` did not match. Server: "x" Client: "y"
A prop rendered on the server differs from the client — usually CSS-in-JS class names or random IDs.
Next.js: Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p> / In HTML, <p> cannot be a descendant of <p>. This will cause a hydration error
The rendered HTML has an invalid element nesting, so the browser "fixes" it and React's hydration no longer matches.
Next.js: ReferenceError: window is not defined (server-side rendering)
Code touching the browser's `window` ran on the server during SSR/build, where it doesn't exist.
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`).
SyntaxError: Unexpected token '<' (HTML served instead of JavaScript)
The browser loaded a .js file but received HTML (an error page or the SPA index.html).
Refused to execute script from 'x' because its MIME type ('text/html') is not executable
The browser fetched a script but the server labelled it text/html (usually an error page), so it refused to run it.
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
TypeError: Missing parameter name at 1 (path-to-regexp)
An Express 5 (path-to-regexp v8) route uses old wildcard syntax like '*' or '/:id?'.
No routes matched location "/x"
React Router found no route definition for the current URL.
Error: NextRouter was not mounted.
next/router’s useRouter was used inside the App Router (app/ directory), which uses next/navigation instead.
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.
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 context.
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.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError