Error map
TS2792: Cannot find module — did you mean to set the 'moduleResolution' option to 'nodenext' 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 · 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)
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 TS2305: Module '"./utils"' has no exported member 'helper'.
You imported a named export that the module doesn't export.
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 TS1259: Module '"express"' can only be default-imported using the 'esModuleInterop' flag
You default-import a CommonJS module that uses `export =`, but `esModuleInterop` isn't enabled.
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).
TypeScript: error TS2614: Module '"./Button"' has no exported member 'Button'. Did you mean to use 'import Button from "./Button"' instead?
You used a named import for something that's a default export (or reverse).
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 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 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 TS17004: Cannot use JSX unless the '--jsx' flag is provided.
A `.tsx` file contains JSX but tsconfig has no `jsx` option.
TypeScript: error TS1192: Module '"./utils"' has no default export.
You used `import x from "./mod"` but the module only has named exports.
TypeScript: error TS5095
`moduleResolution: "bundler"` needs a compatible `module` setting.
Two steps away (26)
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.
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"
Node tried to run a TypeScript file as ESM without a TypeScript loader.
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.
TypeScript: error TS2451: Cannot redeclare block-scoped variable 'name'.
A `let`/`const`/`class` name was declared twice in the same scope — often because files are global scripts sharing one scope.
TypeScript: error TS2307: Cannot find module './App.vue' or its corresponding type declarations.
TypeScript doesn't know what a `.vue` import is without a shim or Volar/`vue-tsc`.
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.
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.
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './x' is not defined by "exports"
You imported a deep path inside a package that its package.json "exports" field doesn’t expose.
TypeScript: error TS2531: Object is possibly 'null'.
You used a value that can be `null` without checking it first (strictNullChecks).
TypeScript: error TS2551: Property 'lenght' does not exist on type 'string'. Did you mean 'length'?
A property name is misspelled (TypeScript suggests the closest valid one).
TypeError: x is not a function
You called something as a function, but its value is not a function (it’s undefined, a string, an object…).
TypeError: Router.use() requires a middleware function but got a Object
app.use()/router.use() received an object instead of a function — usually a router module that wasn’t exported.
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.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
A Node API got an argument of the wrong type — usually undefined because an env var or config value is missing.
TS2339: Property 'x' does not exist on type 'Y'.
TypeScript’s type for the object doesn’t include that property.
TS2345: Argument of type 'string | undefined' is not assignable to parameter of type 'string'.
A value’s type doesn’t match the function parameter — commonly a possibly-undefined value passed where a definite one is required.
TypeScript: error TS1005: ';' expected.
The parser hit a syntax error — missing punctuation, mismatched brackets, or an unsupported syntax for your TypeScript version.
TypeScript: error TS1128: Declaration or statement expected.
The parser found a token where a declaration or statement should start — usually stray braces/parentheses or code outside a funct…
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.
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.
TypeError: x is not a constructor
new was used with something that isn’t a class/constructor — usually a wrong import.
ReferenceError: Cannot access 'x' before initialization
A let/const/class was used before its declaration line ran (temporal dead zone) — often a circular import.
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.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError