Error map
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
Vue · layer 1, On your device
Centre: this error. First ring: errors it is linked with (6). 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 (6)
Nuxt: ReferenceError: window is not defined / 500 Internal Server Error during SSR
Code touching browser globals ran on the server during Nuxt SSR.
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`).
Nuxt: [Vue warn]: Hydration completed but contains mismatches.
Server HTML and client render differed; Vue patched the DOM but logs the mismatch.
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).
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.
Two steps away (18)
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.
Vue: [Vue warn]: injection "theme" not found.
`inject("theme")` ran but no ancestor provided it.
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.
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).
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.
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.
[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.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError