Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 1,201 to 1,250 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS7027 | Unreachable code detected. | Error | Reference |
| TS7028 | Unused label. | Error | Reference |
| TS7029 | Fallthrough case in switch. | Error | Reference |
| TS7030 | Not all code paths return a value. | Error | Reference |
| TS7031 | Binding element '{0}' implicitly has an '{1}' type. | Error | Reference |
| TS7032 | Property '{0}' implicitly has type 'any', because its set accessor lacks a parameter type annotation. | Error | Reference |
| TS7033 | Property '{0}' implicitly has type 'any', because its get accessor lacks a return type annotation. | Error | Reference |
| TS7034 | Variable '{0}' implicitly has type '{1}' in some locations where its type cannot be determined. | Error | Reference |
| TS7035 | Try `npm i --save-dev @types/{1}` if it exists or add a new declaration (.d.ts) file containing `declare module '{0}';` | Error | Reference |
| TS7036 | Dynamic import's specifier must be of type 'string', but here has type '{0}'. | Error | Reference |
| TS7039 | Mapped object type implicitly has an 'any' template type. | Error | Reference |
| TS7040 | If the '{0}' package actually exposes this module, consider sending a pull request to amend... | Error | Reference |
| TS7041 | The containing arrow function captures the global value of 'this'. | Error | Reference |
| TS7042 | Module '{0}' was resolved to '{1}', but '--resolveJsonModule' is not used. | Error | Reference |
| TS7043 | Variable '{0}' implicitly has an '{1}' type, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7044 | Parameter '{0}' implicitly has an '{1}' type, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7045 | Member '{0}' implicitly has an '{1}' type, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7046 | Variable '{0}' implicitly has type '{1}' in some locations, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7047 | Rest parameter '{0}' implicitly has an 'any[]' type, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7048 | Property '{0}' implicitly has type 'any', but a better type for its get accessor may be inferred from usage. | Suggestion | Reference |
| TS7049 | Property '{0}' implicitly has type 'any', but a better type for its set accessor may be inferred from usage. | Suggestion | Reference |
| TS7050 | '{0}' implicitly has an '{1}' return type, but a better type may be inferred from usage. | Suggestion | Reference |
| TS7051 | Parameter has a name but no type. Did you mean '{0}: {1}'? | Error | Reference |
| TS7052 | Element implicitly has an 'any' type because type '{0}' has no index signature. Did you mean to call '{1}'? | Error | Reference |
| TS7053 | Element implicitly has an 'any' type because expression of type '{0}' can't be used to index type '{1}'. | Error | Reference |
| TS7054 | No index signature with a parameter of type '{0}' was found on type '{1}'. | Error | Reference |
| TS7055 | '{0}', which lacks return-type annotation, implicitly has an '{1}' yield type. | Error | Reference |
| TS7056 | The inferred type of this node exceeds the maximum length the compiler will serialize. An explicit type annotation is needed. | Error | Reference |
| TS7057 | 'yield' expression implicitly results in an 'any' type because its containing generator lacks a return-type annotation. | Error | Reference |
| TS7058 | If the '{0}' package actually exposes this module, try adding a new declaration (.d.ts) file containing `declare module '{1}';` | Error | Reference |
| TS7059 | This syntax is reserved in files with the .mts or .cts extension. Use an `as` expression instead. | Error | Reference |
| TS7060 | This syntax is reserved in files with the .mts or .cts extension. Add a trailing comma or explicit constraint. | Error | Reference |
| TS7061 | A mapped type may not declare properties or methods. | Error | Reference |
| TS7080 | Declaration emit elides private members, but '{0}' refers to a private member. Write an explicit type here. | Error | Reference |
| TS8000 | You cannot rename this element. | Error | Reference |
| TS8001 | You cannot rename elements that are defined in the standard TypeScript library. | Error | Reference |
| TS8002 | 'import ... =' can only be used in TypeScript files. | Error | Reference |
| TS8003 | 'export =' can only be used in TypeScript files. | Error | Reference |
| TS8004 | Type parameter declarations can only be used in TypeScript files. | Error | Reference |
| TS8005 | 'implements' clauses can only be used in TypeScript files. | Error | Reference |
| TS8006 | '{0}' declarations can only be used in TypeScript files. | Error | Reference |
| TS8008 | Type aliases can only be used in TypeScript files. | Error | Reference |
| TS8009 | The '{0}' modifier can only be used in TypeScript files. | Error | Reference |
| TS8010 | Type annotations can only be used in TypeScript files. | Error | Reference |
| TS8011 | Type arguments can only be used in TypeScript files. | Error | Reference |
| TS8012 | Parameter modifiers can only be used in TypeScript files. | Error | Reference |
| TS8013 | Non-null assertions can only be used in TypeScript files. | Error | Reference |
| TS8016 | Type assertion expressions can only be used in TypeScript files. | Error | Reference |
| TS8017 | Signature declarations can only be used in TypeScript files. | Error | Reference |
| TS8020 | JSDoc types can only be used inside documentation comments. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest