Error map
TS17004: Cannot use JSX unless the '--jsx' flag is provided TypeScript: error TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript · 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)
Error: Objects are not valid as a React child
You tried to render a plain object (or a Promise/Date) directly in JSX; React can only render strings, numbers, elements and arra…
ReferenceError: React is not defined / 'React' must be in scope when using JSX
JSX was compiled with the classic runtime, which needs React imported in every file.
Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render.
A function (usually a component itself) was rendered instead of calling/rendering it as an element.
Error: Nothing was returned from render. This usually means a return statement is missing.
A component returned undefined (React 17 and earlier) — usually a missing return or a return followed by a line break.
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: Invalid DOM property `class`. Did you mean `className`?
HTML attribute names were used in JSX instead of their React/DOM property names.
Warning: Received `true` for a non-boolean attribute `x`.
A boolean was passed to a DOM attribute that expects a string, or a custom prop leaked through to a DOM element.
TypeScript: error TS2802: Type 'Set<string>' can only be iterated through when using the '--downlevelIteration' flag or with a '--target' of 'es2015' or higher
You iterate a Set/Map/generator with an old compile target (ES5) where `for...of`/spread aren't natively supported.
TypeScript: error TS6059: File '/app/shared/util.ts' is not under 'rootDir' '/app/src'. 'rootDir' is expected to contain all source files.
A source file lives outside the configured `rootDir`, so `tsc` can't preserve the output structure.
TypeScript: error TS2686: 'React' refers to a UMD global, but the current file is a module. Consider adding an import instead.
JSX compiled with `jsx: react` needs `React` imported, but the file doesn't import it.
TypeScript: error TS1005: ';' expected.
The parser hit a syntax error — missing punctuation, mismatched brackets, or an unsupported syntax for your TypeScript version.
TypeScript: error TS2604: JSX element type 'Foo' does not have any construct or call signatures.
You used something as a JSX component that TypeScript doesn't see as a component (not a function/class returning JSX).
Two steps away (33)
TypeError: Cannot read properties of undefined (reading 'x')
You tried to access a property on a value that is `undefined` (or `null`) — usually data that hasn’t loaded yet or a wrong proper…
Error: Too many re-renders. React limits the number of renders to prevent an infinite loop.
A state update runs during render, which triggers another render, which updates state again — forever.
Warning: Each child in a list should have a unique "key" prop
When rendering a list with `.map()`, each element needs a stable, unique `key` so React can track items between renders.
ReferenceError: x is not defined
Code refers to a variable or function name that doesn’t exist in the current scope.
API Error: Invalid or unsupported API version
The API version you requested — in the URL, a header or the SDK config — doesn’t exist or has been retired.
API Error: Feature not enabled for this account (feature_not_enabled / not available on your plan)
The endpoint or option exists, but your account, plan, region or project hasn’t been granted access to it.
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined
JSX referenced a component that is undefined — almost always a default/named import mismatch.
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: A component suspended while responding to synchronous input.
A component suspended (lazy load or data fetch) during an update that wasn’t wrapped in a transition, and there is no Suspense bo…
SyntaxError: Invalid regular expression: /x/: Unterminated group
A regex pattern has invalid syntax — unbalanced parentheses/brackets or unescaped special characters.
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>.
The JSX produces invalid HTML nesting, which also causes hydration mismatches in SSR.
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.
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.
Error: createRoot(...): Target container is not a DOM element.
The element passed to createRoot/render doesn’t exist when the script runs.
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.
Warning: `key` is not a prop. Trying to access it will result in `undefined` being returned.
A component tried to read props.key, which React reserves and never passes down.
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.
Next.js: Error: Failed prop type: The prop `href` expects a `string` or `object` in `<Link>`, but got `undefined` instead
`` received `undefined` (or another invalid value), so Next.js can't build the link.
TS2304: Cannot find name 'x'.
TypeScript doesn’t know an identifier — a missing import, missing type definitions (e.g. for Node or Jest globals), or a typo.
TypeScript: error TS2688: Cannot find type definition file for 'node'.
`types` in tsconfig (or auto-included `@types/*`) refers to a package that isn't installed.
TypeScript: error TS2792: Cannot find module 'x'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?
TypeScript can't resolve a package because `moduleResolution` doesn't match how the package exports (package `exports` map) or pa…
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.
TypeScript: error TS5083: Cannot read file '/app/tsconfig.json'. / error TS6053: File 'tsconfig.base.json' not found
tsc/your IDE can't find or parse the tsconfig (wrong directory, bad `extends`, JSON error).
TypeScript: error TS5095
`moduleResolution: "bundler"` needs a compatible `module` setting.
Next.js: Error: Invalid hook call. Hooks can only be called inside of the body of a function component — Cannot read properties of null (reading 'useContext')
Two copies of React are loaded (or React/ReactDOM versions differ), so hooks can't find the active renderer.
npm: ERESOLVE unable to resolve dependency tree — Found: react@19.0.0 / Could not resolve dependency: peer react@"^18.2.0" from some-lib
A package requires a React version different from the one installed with Next.js.
TypeScript: error TS1192: Module '"./utils"' has no default export.
You used `import x from "./mod"` but the module only has named exports.
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).
SyntaxError: Unexpected end of input
The parser reached the end of the code (or JSON) while still expecting more — a missing } ) ] or empty JSON.
SyntaxError: missing ) after argument list
A function call’s parentheses are unbalanced — often an unescaped quote or a missing comma/plus.
TypeScript: error TS2349: This expression is not callable. Type 'X' has no call signatures.
You called something TypeScript believes isn't a function (a union without compatible signatures, a module namespace, an object).
TypeScript: error TS2503: Cannot find namespace 'JSX'. / Cannot find namespace 'NodeJS'
Code references a global namespace (JSX, NodeJS, Express) that isn't declared — missing `@types` or lib settings.
TypeScript: error TS1208: 'index.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement
With `isolatedModules`, every file must be a module (have an import or export).
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError