Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 301 to 350 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS1379 | An import alias cannot reference a declaration that was exported using 'export type'. | Error | Reference |
| TS1380 | An import alias cannot reference a declaration that was imported using 'import type'. | Error | Reference |
| TS1381 | Unexpected token. Did you mean `{'}'}` or `}`? | Error | Reference |
| TS1382 | Unexpected token. Did you mean `{'>'}` or `>`? | Error | Reference |
| TS1385 | Function type notation must be parenthesized when used in a union type. | Error | Reference |
| TS1386 | Constructor type notation must be parenthesized when used in a union type. | Error | Reference |
| TS1387 | Function type notation must be parenthesized when used in an intersection type. | Error | Reference |
| TS1388 | Constructor type notation must be parenthesized when used in an intersection type. | Error | Reference |
| TS1389 | '{0}' is not allowed as a variable declaration name. | Error | Reference |
| TS1390 | '{0}' is not allowed as a parameter name. | Error | Reference |
| TS1392 | An import alias cannot use 'import type' | Error | Reference |
| TS1431 | 'for await' loops are only allowed at the top level of a file when that file is a module, but this file has no imports or exports.... | Error | Reference |
| TS1432 | Top-level 'for await' loops are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', 'node18',... | Error | Reference |
| TS1433 | Neither decorators nor modifiers may be applied to 'this' parameters. | Error | Reference |
| TS1434 | Unexpected keyword or identifier. | Error | Reference |
| TS1435 | Unknown keyword or identifier. Did you mean '{0}'? | Error | Reference |
| TS1436 | Decorators must precede the name and all keywords of property declarations. | Error | Reference |
| TS1437 | Namespace must be given a name. | Error | Reference |
| TS1438 | Interface must be given a name. | Error | Reference |
| TS1439 | Type alias must be given a name. | Error | Reference |
| TS1440 | Variable declaration not allowed at this location. | Error | Reference |
| TS1441 | Cannot start a function call in a type annotation. | Error | Reference |
| TS1442 | Expected '=' for property initializer. | Error | Reference |
| TS1443 | Module declaration names may only use ' or " quoted strings. | Error | Reference |
| TS1448 | '{0}' resolves to a type-only declaration and must be re-exported using a type-only re-export when '{1}' is enabled. | Error | Reference |
| TS1451 | Private identifiers are only allowed in class bodies and may only be used as part of a class member declaration, property access, or on... | Error | Reference |
| TS1453 | `resolution-mode` should be either `require` or `import`. | Error | Reference |
| TS1454 | `resolution-mode` can only be set for type-only imports. | Error | Reference |
| TS1455 | `resolution-mode` is the only valid key for type import assertions. | Error | Reference |
| TS1456 | Type import assertions should have exactly one key - `resolution-mode` - with value `import` or `require`. | Error | Reference |
| TS1470 | The 'import.meta' meta-property is not allowed in files which will build into CommonJS output. | Error | Reference |
| TS1471 | Module '{0}' cannot be imported using this construct. The specifier only resolves to an ES module, which cannot be imported with... | Error | Reference |
| TS1472 | 'catch' or 'finally' expected. | Error | Reference |
| TS1473 | An import declaration can only be used at the top level of a module. | Error | Reference |
| TS1474 | An export declaration can only be used at the top level of a module. | Error | Reference |
| TS1477 | An instantiation expression cannot be followed by a property access. | Error | Reference |
| TS1478 | Identifier or string literal expected. | Error | Reference |
| TS1479 | The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and... | Error | Reference |
| TS1484 | '{0}' is a type and must be imported using a type-only import when 'verbatimModuleSyntax' is enabled. | Error | Reference |
| TS1485 | '{0}' resolves to a type-only declaration and must be imported using a type-only import when 'verbatimModuleSyntax' is enabled. | Error | Reference |
| TS1486 | Decorator used before 'export' here. | Error | Reference |
| TS1487 | Octal escape sequences are not allowed. Use the syntax '{0}'. | Error | Reference |
| TS1488 | Escape sequence '{0}' is not allowed. | Error | Reference |
| TS1489 | Decimals with leading zeros are not allowed. | Error | Reference |
| TS1490 | File appears to be binary. | Error | Reference |
| TS1491 | '{0}' modifier cannot appear on a 'using' declaration. | Error | Reference |
| TS1492 | '{0}' declarations may not have binding patterns. | Error | Reference |
| TS1493 | The left-hand side of a 'for...in' statement cannot be a 'using' declaration. | Error | Reference |
| TS1494 | The left-hand side of a 'for...in' statement cannot be an 'await using' declaration. | Error | Reference |
| TS1495 | '{0}' modifier cannot appear on an 'await using' declaration. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest