Error map
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
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)
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html"
A or dynamic import got HTML back instead of JavaScript.
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.
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).
[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.
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
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.
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: Error: Failed to find Server Action "abc123". This request might be from an older or newer deployment
The browser called a Server Action ID the current server build doesn't know — usually a version skew after a deploy.
Next.js: Error: Could not find a production build in the '.next' directory. Try building your app with 'next build' before starting the production server
`next start` was run without a prior successful `next build` (or the `.next` folder is missing).
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 wrong base path).
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).
Two steps away (36)
Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
App Service started your app but it crashed or never listened on the expected port.
Could not load file or assembly 'X, Version=…' or one of its dependencies
The runtime couldn’t find or load a referenced DLL — missing from the output, wrong version, or wrong platform (x86/x64).
PHP still runs old code after deploy (OPcache not reset)
OPcache keeps serving cached bytecode, so changes uploaded to the server don’t take effect.
The framework 'Microsoft.NETCore.App', version '8.0.0' (x64) was not found. You must install or update .NET to run this application
The machine doesn’t have the .NET runtime version the app was built for (framework-dependent deployment).
Console: Refused to apply style from 'https://…/style.css' because its MIME type ('text/html') is not a supported stylesheet MIME type
The stylesheet URL returned something that is not CSS — usually a 404/HTML error page — and `X-Content-Type-Options: nosniff` mak…
Console: Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script
The browser could not fetch, parse or install the service worker script, or the page is not allowed to register one (HTTPS and sc…
SyntaxError: Unexpected token < in JSON at position 0
`JSON.parse()` / `response.json()` received something that isn’t JSON — very often an HTML error page.
SyntaxError: missing ) after argument list
A function call’s parentheses are unbalanced — often an unescaped quote or a missing comma/plus.
SyntaxError: Identifier 'x' has already been declared
The same let/const/class name was declared twice in the same scope.
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.
DOMException: Failed to execute 'querySelector' on 'Document': 'x' is not a valid selector
The CSS selector string is invalid — often an ID starting with a digit or containing special characters.
Module not found: Can't resolve 'fs' (Next.js / webpack 5)
A Node.js built-in (fs, path, crypto, net) is imported into code that runs in the browser bundle.
Module parse failed: Unexpected token. You may need an appropriate loader to handle this file type
Webpack found syntax it can’t parse because no loader is configured for that file (JSX, TypeScript, CSS, or modern syntax in node…
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).
Firebase Hosting: Page Not Found — This file does not exist and there was no 404.html or index.html found in the document root
A single-page app route returns 404 when opened directly or refreshed, because Firebase Hosting looks for a real file at that pat…
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).
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+).
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.
Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build)
Node ran out of memory while building a large Next.js app (or on a small CI/Vercel runner).
Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 }
During `next build` a page tried to fetch data from a server (often your own app or an API) that isn't running yet.
Next.js: Error: Server actions must be async functions
A function marked `"use server"` isn't declared `async`.
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.
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.
Next.js: Failed to compile. ./src/app/page.tsx 12:7 Error: 'x' is assigned a value but never used. @typescript-eslint/no-unused-vars
`next build` runs ESLint and fails the build on lint errors.
Vue: [plugin:vite:vue] Duplicate attribute. / [vue/no-duplicate-attributes] Duplicate attribute 'class'
The same attribute appears twice on an element in a template.
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.
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.
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: 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.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError