Error map
TS1128: Declaration or statement expected TypeScript: error TS1128: Declaration or statement expected.
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)
SyntaxError: Identifier 'x' has already been declared
The same let/const/class name was declared twice in the same scope.
TS18048: 'x' is possibly 'undefined'. (TS2532: Object is possibly 'undefined'.)
TypeScript requires you to handle the case where a value may be undefined before using it.
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"
Node tried to run a TypeScript file as ESM without a TypeScript loader.
SyntaxError: await is only valid in async functions and the top level bodies of modules
await was used inside a function that isn’t async (or in a classic, non-module script).
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: Invalid or unexpected token
The code contains a character the parser can’t handle — smart quotes, stray characters or an unterminated string.
SyntaxError: Invalid regular expression: /x/: Unterminated group
A regex pattern has invalid syntax — unbalanced parentheses/brackets or unescaped special characters.
SyntaxError: Unexpected identifier
The parser found a name where it expected punctuation — usually a missing comma, operator or quote.
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.
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: missing ) after argument list
A function call’s parentheses are unbalanced — often an unescaped quote or a missing comma/plus.
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.
Two steps away (29)
ReferenceError: x is not defined
Code refers to a variable or function name that doesn’t exist in the current scope.
NameError: name 'x' is not defined
Python doesn’t know the name — it was never assigned/imported in this scope, or it’s misspelled.
ReferenceError: Cannot access 'x' before initialization
A let/const/class was used before its declaration line ran (temporal dead zone) — often a circular import.
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…
TypeError: x is not iterable
for…of, spread or destructuring was used on something that isn’t an array/iterable.
TS7016: Could not find a declaration file for module 'x'. 'x.js' implicitly has an 'any' type.
The JavaScript package has no TypeScript types bundled and no @types package installed.
Error [ERR_REQUIRE_ESM]: require() of ES Module not supported
CommonJS code used `require()` on a package that is ES-module-only (node-fetch 3, chalk 5, nanoid 4, got 12…).
SyntaxError: Cannot use import statement outside a module
An `import` statement ran in a context treated as CommonJS (Node without "type": "module", a browser script without type="module"…
TypeError [ERR_IMPORT_ATTRIBUTE_MISSING]: Module needs an import attribute of "type: json"
An ES module imported a .json file without the required import attribute.
IndentationError: unexpected indent / expected an indented block
Python’s block structure is broken — inconsistent indentation or mixed tabs and spaces.
Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block
A promise rejected and nothing handled it; since Node 15 this crashes the process.
AbortError: The user aborted a request. / signal is aborted without reason
A fetch was cancelled through an AbortController (or the browser cancelled it).
SyntaxError: Unexpected token < in JSON at position 0
`JSON.parse()` / `response.json()` received something that isn’t JSON — very often an HTML error page.
com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `java.util.ArrayList` from Object value
Jackson found JSON whose shape doesn’t match the target Java type (object vs array, string vs number, missing constructor).
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "x", not marked as ignorable
The JSON contains a field your Java class doesn’t have, and Jackson is configured to fail on unknown properties.
SyntaxError: invalid syntax
Python couldn’t parse the code. The caret (^) points at or just after the mistake.
Dockerfile parse error line N: unknown instruction
A line in the Dockerfile doesn’t start with a valid instruction — usually a broken line continuation or a typo.
GraphQL: Syntax Error: Expected Name, found <EOF> / Unexpected }
The GraphQL document is malformed — unbalanced braces, a stray comma/character, or an empty query.
TypeScript: error TS1005: ';' expected.
The parser hit a syntax error — missing punctuation, mismatched brackets, or an unsupported syntax for your TypeScript version.
Vue: [plugin:vite:vue] Element is missing end tag. / Invalid end tag.
The template has unbalanced HTML tags.
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…
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.
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.
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.
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.
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.
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.
TS2339: Property 'x' does not exist on type 'Y'.
TypeScript’s type for the object doesn’t include that property.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError