Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 851 to 900 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS2775 | Assertions require every name in the call target to be declared with an explicit type annotation. | Error | Reference |
| TS2776 | Assertions require the call target to be an identifier or qualified name. | Error | Reference |
| TS2777 | The operand of an increment or decrement operator may not be an optional property access. | Error | Reference |
| TS2778 | The target of an object rest assignment may not be an optional property access. | Error | Reference |
| TS2779 | The left-hand side of an assignment expression may not be an optional property access. | Error | Reference |
| TS2780 | The left-hand side of a 'for...in' statement may not be an optional property access. | Error | Reference |
| TS2781 | The left-hand side of a 'for...of' statement may not be an optional property access. | Error | Reference |
| TS2783 | '{0}' is specified more than once, so this usage will be overwritten. | Error | Reference |
| TS2784 | 'get' and 'set' accessors cannot declare 'this' parameters. | Error | Reference |
| TS2785 | This spread always overwrites this property. | Error | Reference |
| TS2786 | '{0}' cannot be used as a JSX component. | Error | Reference |
| TS2787 | Its return type '{0}' is not a valid JSX element. | Error | Reference |
| TS2788 | Its instance type '{0}' is not a valid JSX element. | Error | Reference |
| TS2789 | Its element type '{0}' is not a valid JSX element. | Error | Reference |
| TS2790 | The operand of a 'delete' operator must be optional. | Error | Reference |
| TS2791 | Exponentiation cannot be performed on 'bigint' values unless the 'target' option is set to 'es2016' or later. | Error | Reference |
| TS2792 | Cannot find module '{0}'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option? | Error | Reference |
| TS2793 | The call would have succeeded against this implementation, but implementation signatures of overloads are not externally visible. | Error | Reference |
| TS2794 | Expected {0} arguments, but got {1}. Did you forget to include 'void' in your type argument to 'Promise'? | Error | Reference |
| TS2795 | The 'intrinsic' keyword can only be used to declare compiler provided intrinsic types. | Error | Reference |
| TS2796 | It is likely that you are missing a comma to separate these two template expressions. They form a tagged template expression which cannot... | Error | Reference |
| TS2797 | A mixin class that extends from a type variable containing an abstract construct signature must also be declared 'abstract'. | Error | Reference |
| TS2798 | The declaration was marked as deprecated here. | Error | Reference |
| TS2799 | Type produces a tuple type that is too large to represent. | Error | Reference |
| TS2800 | Expression produces a tuple type that is too large to represent. | Error | Reference |
| TS2801 | This condition will always return true since this '{0}' is always defined. | Error | Reference |
| TS2802 | Type '{0}' can only be iterated through when using the '--downlevelIteration' flag or with a '--target' of 'es2015' or higher. | Error | Reference |
| TS2803 | Cannot assign to private method '{0}'. Private methods are not writable. | Error | Reference |
| TS2804 | Duplicate identifier '{0}'. Static and instance elements cannot share the same private name. | Error | Reference |
| TS2806 | Private accessor was defined without a getter. | Error | Reference |
| TS2807 | This syntax requires an imported helper named '{1}' with {2} parameters, which is not compatible with the one in '{0}'. Consider upgrading... | Error | Reference |
| TS2808 | A get accessor must be at least as accessible as the setter | Error | Reference |
| TS2809 | Declaration or statement expected. This '=' follows a block of statements, so if you intended to write a destructuring assignment, you... | Error | Reference |
| TS2810 | Expected 1 argument, but got 0. 'new Promise()' needs a JSDoc hint to produce a 'resolve' that can be called without arguments. | Error | Reference |
| TS2811 | Initializer for property '{0}' | Error | Reference |
| TS2812 | Property '{0}' does not exist on type '{1}'. Try changing the 'lib' compiler option to include 'dom'. | Error | Reference |
| TS2813 | Class declaration cannot implement overload list for '{0}'. | Error | Reference |
| TS2814 | Function with bodies can only merge with classes that are ambient. | Error | Reference |
| TS2815 | 'arguments' cannot be referenced in property initializers or class static initialization blocks. | Error | Reference |
| TS2816 | Cannot use 'this' in a static property initializer of a decorated class. | Error | Reference |
| TS2817 | Property '{0}' has no initializer and is not definitely assigned in a class static block. | Error | Reference |
| TS2818 | Duplicate identifier '{0}'. Compiler reserves name '{1}' when emitting 'super' references in static initializers. | Error | Reference |
| TS2819 | Namespace name cannot be '{0}'. | Error | Reference |
| TS2820 | Type '{0}' is not assignable to type '{1}'. Did you mean '{2}'? | Error | Reference |
| TS2821 | Import assertions are only supported when the '--module' option is set to 'esnext', 'node18', 'node20', 'nodenext', or 'preserve'. | Error | Reference |
| TS2822 | Import assertions cannot be used with type-only imports or exports. | Error | Reference |
| TS2823 | Import attributes are only supported when the '--module' option is set to 'esnext', 'node18', 'node20', 'nodenext', or 'preserve'. | Error | Reference |
| TS2833 | Cannot find namespace '{0}'. Did you mean '{1}'? | Error | Reference |
| TS2834 | Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider... | Error | Reference |
| TS2835 | Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you... | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest