Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 1,351 to 1,400 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS18033 | Type '{0}' is not assignable to type '{1}' as required for computed enum member values. | Error | Reference |
| TS18035 | Invalid value for 'jsxFragmentFactory'. '{0}' is not a valid identifier or qualified-name. | Error | Reference |
| TS18036 | Class decorators can't be used with static private identifier. Consider removing the experimental decorator. | Error | Reference |
| TS18037 | 'await' expression cannot be used inside a class static block. | Error | Reference |
| TS18038 | 'for await' loops cannot be used inside a class static block. | Error | Reference |
| TS18039 | Invalid use of '{0}'. It cannot be used inside a class static block. | Error | Reference |
| TS18041 | A 'return' statement cannot be used inside a class static block. | Error | Reference |
| TS18042 | '{0}' is a type and cannot be imported in JavaScript files. Use '{1}' in a JSDoc type annotation. | Error | Reference |
| TS18043 | Types cannot appear in export declarations in JavaScript files. | Error | Reference |
| TS18045 | Properties with the 'accessor' modifier are only available when targeting ECMAScript 2015 and higher. | Error | Reference |
| TS18046 | '{0}' is of type 'unknown'. | Error | Reference |
| TS18047 | '{0}' is possibly 'null'. | Error | Reference |
| TS18048 | '{0}' is possibly 'undefined'. | Error | Reference |
| TS18049 | '{0}' is possibly 'null' or 'undefined'. | Error | Reference |
| TS18050 | The value '{0}' cannot be used here. | Error | Reference |
| TS18051 | Compiler option '{0}' cannot be given an empty string. | Error | Reference |
| TS18053 | Its type '{0}' is not a valid JSX element type. | Error | Reference |
| TS18054 | 'await using' statements cannot be used inside a class static block. | Error | Reference |
| TS18055 | '{0}' has a string type, but must have syntactically recognizable string syntax when 'isolatedModules' is enabled. | Error | Reference |
| TS18056 | Enum member following a non-literal numeric member must have an initializer when 'isolatedModules' is enabled. | Error | Reference |
| TS18057 | String literal import and export names are not supported when the '--module' flag is set to 'es2015' or 'es2020'. | Error | Reference |
| TS18058 | Default imports are not allowed in a deferred import. | Error | Reference |
| TS18059 | Named imports are not allowed in a deferred import. | Error | Reference |
| TS18060 | Deferred imports are only supported when the '--module' flag is set to 'esnext' or 'preserve'. | Error | Reference |
| TS18061 | '{0}' is not a valid meta-property for keyword 'import'. Did you mean 'meta' or 'defer'? | Error | Reference |
| TS18062 | Regular expression pattern modifiers are only available when targeting '{0}' or later. | Error | Reference |
| TS18063 | Duplicate named capturing groups are only available when targeting '{0}' or later. | Error | Reference |
| TS18064 | Private identifiers cannot be used in destructuring patterns. | Error | Reference |
| TS18065 | Content mapper file extension '{0}' must begin with a '.'. | Error | Reference |
| TS18066 | Content mapper file extension '{0}' is a built-in extension and cannot be registered by a content mapper. | Error | Reference |
| TS18067 | Content mapper file extension '{0}' is registered by more than one content mapper. | Error | Reference |
| TS18068 | Content mappers require the '--runExternalCode' command line flag to be enabled. | Error | Reference |
| TS18069 | The content mapper '{0}' failed to transform this file. | Error | Reference |
| TS18070 | The content mapper '{0}' failed {1} times and will not be used. | Error | Reference |
| TS18071 | The content mapper '{0}' did not provide the required position mappings. | Error | Reference |
| TS18072 | The content mapper '{0}' produced a position mapping that points outside the original content (original offset {1}). | Error | Reference |
| TS18073 | The content mapper '{0}' produced a verbatim mapping that does not match the original content (virtual offset {1}, original offset {2}). | Error | Reference |
| TS18075 | The content mapper package '{0}' could not be resolved. | Error | Reference |
| TS18076 | The 'package.json' of the content mapper package '{0}' could not be parsed. | Error | Reference |
| TS18077 | The 'package.json' of the content mapper package '{0}' does not specify a 'name'. | Error | Reference |
| TS18078 | The 'package.json' of the content mapper package '{0}' does not declare a 'typescript.contentMapper' object. | Error | Reference |
| TS18079 | The 'typescript.contentMapper.exec' of the content mapper package '{0}' must be a non-empty array of strings. | Error | Reference |
| TS18080 | Virtual code produced by the content mapper '{0}' has problems with no corresponding location in this file. | Error | Reference |
| TS18081 | The content mapper '{0}' produced overlapping or out-of-order position mappings (near virtual offset {1}). | Error | Reference |
| TS18082 | The content mapper '{0}' produced invalid mapping features near original offset {1}. | Error | Reference |
| TS18083 | The content mapper '{0}' produced a position mapping with an invalid kind (near virtual offset {1}). | Error | Reference |
| TS18099 | The content mapper '{0}' could not be initialized. | Error | Reference |
| TS80001 | File is a CommonJS module; it may be converted to an ES module. | Suggestion | Reference |
| TS80002 | This constructor function may be converted to a class declaration. | Suggestion | Reference |
| TS80003 | Import may be converted to a default import. | Suggestion | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest