Error map
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
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)
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.
Nuxt: ReferenceError: window is not defined / 500 Internal Server Error during SSR
Code touching browser globals ran on the server during Nuxt SSR.
Next.js: ⨯ Conflicting app and page file was found, please remove the conflicting files to continue: "pages/index.tsx" - "app/page.tsx"
The same URL is defined in both the `app` and `pages` directories.
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.
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-existent files.
Next.js: Error: You cannot use different slug names for the same dynamic path ('id' !== 'slug')
Sibling dynamic folders at the same level use different parameter names.
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).
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).
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.
Two steps away (34)
HTTP 404 Not Found
The server can’t find anything at the requested URL.
HTTP 405 Method Not Allowed
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).
Whitelabel Error Page — This application has no explicit mapping for /error
Spring Boot’s default error page — the request hit no controller mapping (404) or a controller threw (500).
Error: useNavigate() may be used only in the context of a <Router> component.
A React Router hook ran in a component that isn’t rendered inside a Router provider.
API Error: Cannot GET /api/... / No route matches / The route could not be found
The server has no route for this URL and HTTP method combination — the endpoint path, API version prefix or method is wrong.
connect: Network is unreachable (ENETUNREACH)
The host has no route to the destination network — no default gateway, interface down, or trying IPv6 without IPv6 connectivity.
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.
You're importing a component that needs useState. It only works in a Client Component but none of its parents are marked with "use client"
In the Next.js App Router, a component using hooks or browser APIs is rendered as a Server Component.
Error: Dynamic server usage: Route /x couldn't be rendered statically because it used `cookies`
Next.js tried to statically render a route that reads request-specific data (cookies, headers, searchParams).
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.
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.
Error occurred prerendering page "/x". Read more: https://nextjs.org/docs/messages/prerender-error
A page threw an error while Next.js was rendering it at build time.
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]: 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).
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.
Next.js: You're importing a component that needs createContext. It only works in a Client Component but none of its parents are marked with "use client"
A context provider (or a lib that uses `createContext`) is used in a Server Component.
Next.js 15: Error: Route "/blog/[slug]" used `params.slug`. `params` should be awaited before using its properties
In Next.js 15 `params` and `searchParams` are Promises; reading properties synchronously triggers this error/warning.
Next.js: Page "/blog/[slug]" is missing "generateStaticParams()" so it cannot be used with "output: export" config
A dynamic route can't be statically exported without telling Next.js which paths to generate.
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 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.
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.
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).
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] 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.
Next.js: ReferenceError: document is not defined
Code used the DOM (`document`) while rendering on the server.
Next.js: ReferenceError: localStorage is not defined / sessionStorage is not defined
`localStorage`/`sessionStorage` was read during server rendering.
Next.js: TypeError: Failed to parse URL from /api/posts (fetch in a Server Component)
`fetch('/api/x')` with a relative URL works in browsers but not on the server, which has no base URL.
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`).
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError