Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 401 to 450 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS1546 | 'await using' declarations are not allowed in ambient contexts. | Error | Reference |
| TS1547 | 'using' declarations are not allowed in 'case' or 'default' clauses unless contained within a block. | Error | Reference |
| TS1548 | 'await using' declarations are not allowed in 'case' or 'default' clauses unless contained within a block. | Error | Reference |
| TS1550 | An ambient module declaration with import attributes must use a pattern name with an '*' character. | Error | Reference |
| TS1551 | Import attributes are not allowed on a module augmentation. | Error | Reference |
| TS1552 | An import attributes type may only contain property signatures. | Error | Reference |
| TS1553 | An import attributes property must have a type annotation. | Error | Reference |
| TS1554 | An import attributes property must have a string literal or identifier name. | Error | Reference |
| TS1555 | An import attributes property must have a string literal type annotation. | Error | Reference |
| TS1556 | An import attributes property cannot be optional. | Error | Reference |
| TS1557 | '{0}' is not a valid key for an import attributes type. | Error | Reference |
| TS1558 | An import attributes property cannot have a 'readonly' modifier. | Error | Reference |
| TS2200 | The types of '{0}' are incompatible between these types. | Error | Reference |
| TS2201 | The types returned by '{0}' are incompatible between these types. | Error | Reference |
| TS2202 | Call signature return types '{0}' and '{1}' are incompatible. | Error | Reference |
| TS2203 | Construct signature return types '{0}' and '{1}' are incompatible. | Error | Reference |
| TS2204 | Call signatures with no arguments have incompatible return types '{0}' and '{1}'. | Error | Reference |
| TS2205 | Construct signatures with no arguments have incompatible return types '{0}' and '{1}'. | Error | Reference |
| TS2206 | The 'type' modifier cannot be used on a named import when 'import type' is used on its import statement. | Error | Reference |
| TS2207 | The 'type' modifier cannot be used on a named export when 'export type' is used on its export statement. | Error | Reference |
| TS2208 | This type parameter might need an `extends {0}` constraint. | Error | Reference |
| TS2209 | The project root is ambiguous, but is required to resolve export map entry '{0}' in file '{1}'. Supply the `rootDir` compiler option to... | Error | Reference |
| TS2210 | The project root is ambiguous, but is required to resolve import map entry '{0}' in file '{1}'. Supply the `rootDir` compiler option to... | Error | Reference |
| TS2300 | Duplicate identifier '{0}'. | Error | Reference |
| TS2301 | Initializer of instance member variable '{0}' cannot reference identifier '{1}' declared in the constructor. | Error | Reference |
| TS2302 | Static members cannot reference class type parameters. | Error | Reference |
| TS2303 | Circular definition of import alias '{0}'. | Error | Reference |
| TS2304 | Cannot find name '{0}'. | Error | Reference |
| TS2305 | Module '{0}' has no exported member '{1}'. | Error | Reference |
| TS2306 | File '{0}' is not a module. | Error | Reference |
| TS2307 | Cannot find module '{0}' or its corresponding type declarations. | Error | Reference |
| TS2308 | Module {0} has already exported a member named '{1}'. Consider explicitly re-exporting to resolve the ambiguity. | Error | Reference |
| TS2309 | An export assignment cannot be used in a module with other exported elements. | Error | Reference |
| TS2310 | Type '{0}' recursively references itself as a base type. | Error | Reference |
| TS2311 | Cannot find name '{0}'. Did you mean to write this in an async function? | Error | Reference |
| TS2312 | An interface can only extend an object type or intersection of object types with statically known members. | Error | Reference |
| TS2313 | Type parameter '{0}' has a circular constraint. | Error | Reference |
| TS2314 | Generic type '{0}' requires {1} type argument(s). | Error | Reference |
| TS2315 | Type '{0}' is not generic. | Error | Reference |
| TS2316 | Global type '{0}' must be a class or interface type. | Error | Reference |
| TS2317 | Global type '{0}' must have {1} type parameter(s). | Error | Reference |
| TS2318 | Cannot find global type '{0}'. | Error | Reference |
| TS2319 | Named property '{0}' of types '{1}' and '{2}' are not identical. | Error | Reference |
| TS2320 | Interface '{0}' cannot simultaneously extend types '{1}' and '{2}'. | Error | Reference |
| TS2321 | Excessive stack depth comparing types '{0}' and '{1}'. | Error | Reference |
| TS2322 | Type '{0}' is not assignable to type '{1}'. | Error | Reference |
| TS2323 | Cannot redeclare exported variable '{0}'. | Error | Reference |
| TS2324 | Property '{0}' is missing in type '{1}'. | Error | Reference |
| TS2325 | Property '{0}' is private in type '{1}' but not in type '{2}'. | Error | Reference |
| TS2326 | Types of property '{0}' are incompatible. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest