Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 551 to 600 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS2437 | Module '{0}' is hidden by a local declaration with the same name. | Error | Reference |
| TS2438 | Import name cannot be '{0}'. | Error | Reference |
| TS2439 | Import or export declaration in an ambient module declaration cannot reference module through relative module name. | Error | Reference |
| TS2440 | Import declaration conflicts with local declaration of '{0}'. | Error | Reference |
| TS2441 | Duplicate identifier '{0}'. Compiler reserves name '{1}' in top level scope of a module. | Error | Reference |
| TS2442 | Types have separate declarations of a private property '{0}'. | Error | Reference |
| TS2443 | Property '{0}' is protected but type '{1}' is not a class derived from '{2}'. | Error | Reference |
| TS2444 | Property '{0}' is protected in type '{1}' but public in type '{2}'. | Error | Reference |
| TS2445 | Property '{0}' is protected and only accessible within class '{1}' and its subclasses. | Error | Reference |
| TS2446 | Property '{0}' is protected and only accessible through an instance of class '{1}'. This is an instance of class '{2}'. | Error | Reference |
| TS2447 | The '{0}' operator is not allowed for boolean types. Consider using '{1}' instead. | Error | Reference |
| TS2448 | Block-scoped variable '{0}' used before its declaration. | Error | Reference |
| TS2449 | Class '{0}' used before its declaration. | Error | Reference |
| TS2450 | Enum '{0}' used before its declaration. | Error | Reference |
| TS2451 | Cannot redeclare block-scoped variable '{0}'. | Error | Reference |
| TS2452 | An enum member cannot have a numeric name. | Error | Reference |
| TS2454 | Variable '{0}' is used before being assigned. | Error | Reference |
| TS2456 | Type alias '{0}' circularly references itself. | Error | Reference |
| TS2457 | Type alias name cannot be '{0}'. | Error | Reference |
| TS2458 | An AMD module cannot have multiple name assignments. | Error | Reference |
| TS2459 | Module '{0}' declares '{1}' locally, but it is not exported. | Error | Reference |
| TS2460 | Module '{0}' declares '{1}' locally, but it is exported as '{2}'. | Error | Reference |
| TS2461 | Type '{0}' is not an array type. | Error | Reference |
| TS2462 | A rest element must be last in a destructuring pattern. | Error | Reference |
| TS2463 | A binding pattern parameter cannot be optional in an implementation signature. | Error | Reference |
| TS2464 | A computed property name must be of type 'string', 'number', 'symbol', or 'any'. | Error | Reference |
| TS2465 | 'this' cannot be referenced in a computed property name. | Error | Reference |
| TS2466 | 'super' cannot be referenced in a computed property name. | Error | Reference |
| TS2467 | A computed property name cannot reference a type parameter from its containing type. | Error | Reference |
| TS2468 | Cannot find global value '{0}'. | Error | Reference |
| TS2469 | The '{0}' operator cannot be applied to type 'symbol'. | Error | Reference |
| TS2472 | Spread operator in 'new' expressions is only available when targeting ECMAScript 5 and higher. | Error | Reference |
| TS2473 | Enum declarations must all be const or non-const. | Error | Reference |
| TS2474 | const enum member initializers must be constant expressions. | Error | Reference |
| TS2475 | 'const' enums can only be used in property or index access expressions or the right hand side of an import declaration or export... | Error | Reference |
| TS2476 | A const enum member can only be accessed using a string literal. | Error | Reference |
| TS2477 | 'const' enum member initializer was evaluated to a non-finite value. | Error | Reference |
| TS2478 | 'const' enum member initializer was evaluated to disallowed value 'NaN'. | Error | Reference |
| TS2480 | 'let' is not allowed to be used as a name in 'let' or 'const' declarations. | Error | Reference |
| TS2481 | Cannot initialize outer scoped variable '{0}' in the same scope as block scoped declaration '{1}'. | Error | Reference |
| TS2483 | The left-hand side of a 'for...of' statement cannot use a type annotation. | Error | Reference |
| TS2484 | Export declaration conflicts with exported declaration of '{0}'. | Error | Reference |
| TS2487 | The left-hand side of a 'for...of' statement must be a variable or a property access. | Error | Reference |
| TS2488 | Type '{0}' must have a '[Symbol.iterator]()' method that returns an iterator. | Error | Reference |
| TS2489 | An iterator must have a 'next()' method. | Error | Reference |
| TS2490 | The type returned by the '{0}()' method of an iterator must have a 'value' property. | Error | Reference |
| TS2491 | The left-hand side of a 'for...in' statement cannot be a destructuring pattern. | Error | Reference |
| TS2492 | Cannot redeclare identifier '{0}' in catch clause. | Error | Reference |
| TS2493 | Tuple type '{0}' of length '{1}' has no element at index '{2}'. | Error | Reference |
| TS2494 | Using a string in a 'for...of' statement is only supported in ECMAScript 5 and higher. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest