Errors
TypeScript errors
TSxxxx compiler errors.
1,407 entries0 written pages
Showing 1,151 to 1,200 of 1,407Source: TypeScript diagnosticMessages.json
| Code | Error | Category | Page |
|---|---|---|---|
| TS6200 | Definitions of the following identifiers conflict with those in another file: {0} | Error | Reference |
| TS6202 | Project references may not form a circular graph. Cycle detected: {0} | Error | Reference |
| TS6205 | All type parameters are unused. | Error | Reference |
| TS6229 | Tag '{0}' expects at least '{1}' arguments, but the JSX factory '{2}' provides at most '{3}'. | Error | Reference |
| TS6230 | Option '{0}' can only be specified in 'tsconfig.json' file or set to 'false' or 'null' on command line. | Error | Reference |
| TS6231 | Could not resolve the path '{0}' with the extensions: {1}. | Error | Reference |
| TS6232 | Declaration augments declaration in another file. This cannot be serialized. | Error | Reference |
| TS6233 | This is the declaration being augmented. Consider moving the augmenting declaration into the same file. | Error | Reference |
| TS6234 | This expression is not callable because it is a 'get' accessor. Did you mean to use it without '()'? | Error | Reference |
| TS6236 | Arguments for the rest parameter '{0}' were not provided. | Error | Reference |
| TS6238 | Specify the module specifier to be used to import the 'jsx' and 'jsxs' factory functions from. eg, react | Error | Reference |
| TS6258 | '{0}' should be set inside the 'compilerOptions' object of the config json file | Error | Reference |
| TS6263 | Module '{0}' was resolved to '{1}', but '--allowArbitraryExtensions' is not set. | Error | Reference |
| TS6266 | Option '{0}' can only be specified on command line. | Error | Reference |
| TS6304 | Composite projects may not disable declaration emit. | Error | Reference |
| TS6305 | Output file '{0}' has not been built from source file '{1}'. | Error | Reference |
| TS6306 | Referenced project '{0}' must have setting "composite": true. | Error | Reference |
| TS6307 | File '{0}' is not listed within the file list of project '{1}'. Projects must list all files or use an 'include' pattern. | Error | Reference |
| TS6310 | Referenced project '{0}' may not disable emit. | Error | Reference |
| TS6369 | Option '--build' must be the first command line argument. | Error | Reference |
| TS6370 | Options '{0}' and '{1}' cannot be combined. | Error | Reference |
| TS6377 | Cannot write file '{0}' because it will overwrite '.tsbuildinfo' file generated by referenced project '{1}' | Error | Reference |
| TS6379 | Composite projects may not disable incremental compilation. | Error | Reference |
| TS6385 | '{0}' is deprecated. | Suggestion | Reference |
| TS6387 | The signature '{0}' of '{1}' is deprecated. | Suggestion | Reference |
| TS6424 | Multiple 'module.exports' assignments cannot be serialized for declaration emit. | Error | Reference |
| TS6425 | Nested CommonJS export constructs cannot be serialized for declaration emit. | Error | Reference |
| TS6504 | File '{0}' is a JavaScript file. Did you mean to enable the 'allowJs' option? | Error | Reference |
| TS6807 | This operation can be simplified. This shift is identical to `{0} {1} {2}`. | Error | Reference |
| TS6931 | List of file name suffixes to search when resolving a module. | Error | Reference |
| TS7005 | Variable '{0}' implicitly has an '{1}' type. | Error | Reference |
| TS7006 | Parameter '{0}' implicitly has an '{1}' type. | Error | Reference |
| TS7008 | Member '{0}' implicitly has an '{1}' type. | Error | Reference |
| TS7009 | 'new' expression, whose target lacks a construct signature, implicitly has an 'any' type. | Error | Reference |
| TS7010 | '{0}', which lacks return-type annotation, implicitly has an '{1}' return type. | Error | Reference |
| TS7011 | Function expression, which lacks return-type annotation, implicitly has an '{0}' return type. | Error | Reference |
| TS7012 | This overload implicitly returns the type '{0}' because it lacks a return type annotation. | Error | Reference |
| TS7013 | Construct signature, which lacks return-type annotation, implicitly has an 'any' return type. | Error | Reference |
| TS7014 | Function type, which lacks return-type annotation, implicitly has an '{0}' return type. | Error | Reference |
| TS7015 | Element implicitly has an 'any' type because index expression is not of type 'number'. | Error | Reference |
| TS7016 | Could not find a declaration file for module '{0}'. '{1}' implicitly has an 'any' type. | Error | Reference |
| TS7017 | Element implicitly has an 'any' type because type '{0}' has no index signature. | Error | Reference |
| TS7018 | Object literal's property '{0}' implicitly has an '{1}' type. | Error | Reference |
| TS7019 | Rest parameter '{0}' implicitly has an 'any[]' type. | Error | Reference |
| TS7020 | Call signature, which lacks return-type annotation, implicitly has an 'any' return type. | Error | Reference |
| TS7022 | '{0}' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer. | Error | Reference |
| TS7023 | '{0}' implicitly has return type 'any' because it does not have a return type annotation and is referenced directly or indirectly in one... | Error | Reference |
| TS7024 | Function implicitly has return type 'any' because it does not have a return type annotation and is referenced directly or indirectly in... | Error | Reference |
| TS7025 | Generator implicitly has yield type '{0}'. Consider supplying a return type annotation. | Error | Reference |
| TS7026 | JSX element implicitly has type 'any' because no interface 'JSX.{0}' exists. | Error | Reference |
Other families: JavaScript, Node.js, npm, React, Next.js, Vite, webpack, Jest