Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 1,301 to 1,350 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS9036 | Move the expression in default export to a variable and add a type annotation to it. | Error | Reference |
| TS9037 | Default exports can't be inferred with --isolatedDeclarations. | Error | Reference |
| TS9038 | Computed property names on class or object literals cannot be inferred with --isolatedDeclarations. | Error | Reference |
| TS9039 | Type containing private name '{0}' can't be used with --isolatedDeclarations. | Error | Reference |
| TS17000 | JSX attributes must only be assigned a non-empty 'expression'. | Error | Reference |
| TS17001 | JSX elements cannot have multiple attributes with the same name. | Error | Reference |
| TS17002 | Expected corresponding JSX closing tag for '{0}'. | Error | Reference |
| TS17004 | Cannot use JSX unless the '--jsx' flag is provided. | Error | Reference |
| TS17005 | A constructor cannot contain a 'super' call when its class extends 'null'. | Error | Reference |
| TS17006 | An unary expression with the '{0}' operator is not allowed in the left-hand side of an exponentiation expression. Consider enclosing the... | Error | Reference |
| TS17007 | A type assertion expression is not allowed in the left-hand side of an exponentiation expression. Consider enclosing the expression in... | Error | Reference |
| TS17008 | JSX element '{0}' has no corresponding closing tag. | Error | Reference |
| TS17009 | 'super' must be called before accessing 'this' in the constructor of a derived class. | Error | Reference |
| TS17010 | Unknown type acquisition option '{0}'. | Error | Reference |
| TS17011 | 'super' must be called before accessing a property of 'super' in the constructor of a derived class. | Error | Reference |
| TS17012 | '{0}' is not a valid meta-property for keyword '{1}'. Did you mean '{2}'? | Error | Reference |
| TS17013 | Meta-property '{0}' is only allowed in the body of a function declaration, function expression, or constructor. | Error | Reference |
| TS17014 | JSX fragment has no corresponding closing tag. | Error | Reference |
| TS17015 | Expected corresponding closing tag for JSX fragment. | Error | Reference |
| TS17016 | The 'jsxFragmentFactory' compiler option must be provided to use JSX fragments with the 'jsxFactory' compiler option. | Error | Reference |
| TS17017 | An @jsxFrag pragma is required when using an @jsx pragma with JSX fragments. | Error | Reference |
| TS17018 | Unknown type acquisition option '{0}'. Did you mean '{1}'? | Error | Reference |
| TS17019 | '{0}' at the end of a type is not valid TypeScript syntax. Did you mean to write '{1}'? | Error | Reference |
| TS17020 | '{0}' at the start of a type is not valid TypeScript syntax. Did you mean to write '{1}'? | Error | Reference |
| TS17021 | Unicode escape sequence cannot appear here. | Error | Reference |
| TS18000 | Circularity detected while resolving configuration: {0} | Error | Reference |
| TS18002 | The 'files' list in config file '{0}' is empty. | Error | Reference |
| TS18003 | No inputs were found in config file '{0}'. Specified 'include' paths were '{1}' and 'exclude' paths were '{2}'. | Error | Reference |
| TS18004 | No value exists in scope for the shorthand property '{0}'. Either declare one or provide an initializer. | Error | Reference |
| TS18006 | Classes may not have a field named 'constructor'. | Error | Reference |
| TS18007 | JSX expressions may not use the comma operator. Did you mean to write an array? | Error | Reference |
| TS18009 | Private identifiers cannot be used as parameters. | Error | Reference |
| TS18010 | An accessibility modifier cannot be used with a private identifier. | Error | Reference |
| TS18011 | The operand of a 'delete' operator cannot be a private identifier. | Error | Reference |
| TS18012 | '#constructor' is a reserved word. | Error | Reference |
| TS18013 | Property '{0}' is not accessible outside class '{1}' because it has a private identifier. | Error | Reference |
| TS18014 | The property '{0}' cannot be accessed on type '{1}' within this class because it is shadowed by another private identifier with the same... | Error | Reference |
| TS18015 | Property '{0}' in type '{1}' refers to a different member that cannot be accessed from within type '{2}'. | Error | Reference |
| TS18016 | Private identifiers are not allowed outside class bodies. | Error | Reference |
| TS18017 | The shadowing declaration of '{0}' is defined here | Error | Reference |
| TS18018 | The declaration of '{0}' that you probably intended to use is defined here | Error | Reference |
| TS18019 | '{0}' modifier cannot be used with a private identifier. | Error | Reference |
| TS18024 | An enum member cannot be named with a private identifier. | Error | Reference |
| TS18026 | '#!' can only be used at the start of a file. | Error | Reference |
| TS18027 | Compiler reserves name '{0}' when emitting private identifier downlevel. | Error | Reference |
| TS18028 | Private identifiers are only available when targeting ECMAScript 2015 and higher. | Error | Reference |
| TS18029 | Private identifiers are not allowed in variable declarations. | Error | Reference |
| TS18030 | An optional chain cannot contain private identifiers. | Error | Reference |
| TS18031 | The intersection '{0}' was reduced to 'never' because property '{1}' has conflicting types in some constituents. | Error | Reference |
| TS18032 | The intersection '{0}' was reduced to 'never' because property '{1}' exists in multiple constituents and is private in some. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest