| TypeScript | |
| Paradigm: | Multi-paradigm |
| Released: | [1] |
| Designer: | Microsoft |
| Developer: | Microsoft |
| Typing: | Duck, gradual, structural[2] |
| Influenced By: | C#, F#,[3] Java, JavaScript, ActionScript[4] |
| Influenced: | AtScript, AssemblyScript, ArkTS |
| License: | Apache License 2.0 |
| File Ext: | .ts, .tsx, .mts, .cts |
TypeScript is a free and open-source high-level programming language developed by Microsoft that adds static typing with optional type annotations to JavaScript. It is designed for the development of large applications and transpiles to JavaScript.[5] .
TypeScript may be used to develop JavaScript applications for both client-side and server-side execution (as with Node.js, Deno or Bun). Multiple options are available for transpilation. The default TypeScript Compiler can be used,[6] or the Babel compiler can be invoked to convert TypeScript to JavaScript.
TypeScript supports definition files that can contain type information of existing JavaScript libraries, much like C++ header files can describe the structure of existing object files. This enables other programs to use the values defined in the files as if they were statically typed TypeScript entities. There are third-party header files for popular libraries such as jQuery, MongoDB, and D3.js. TypeScript headers for the Node.js library modules are also available, allowing development of Node.js programs within TypeScript.[7]
The TypeScript compiler is itself written in TypeScript and compiled to JavaScript. It is licensed under the Apache License 2.0. Anders Hejlsberg, lead architect of C# and creator of Delphi and Turbo Pascal, has worked on the development of TypeScript.[8] [9] [10] [11]
TypeScript was released to the public in October 2012, with version 0.8, after two years of internal development at Microsoft.[12] [13] Soon after the initial public release, Miguel de Icaza praised the language itself, but criticized the lack of mature IDE support apart from Microsoft Visual Studio, which was not available on Linux and macOS at the time.[14] [15] As of April 2021 there is support in other IDEs and text editors, including Emacs, Vim, WebStorm, Atom[16] and Microsoft's own Visual Studio Code.[17] TypeScript 0.9, released in 2013, added support for generics.[18]
TypeScript 1.0 was released at Microsoft's Build developer conference in 2014.[19] Visual Studio 2013 Update 2 provided built-in support for TypeScript.[20] Further improvement were made in July 2014, when the development team announced a new TypeScript compiler, asserted to have a five-fold performance increase. Simultaneously, the source code, which was initially hosted on CodePlex, was moved to GitHub.[21]
On 22 September 2016, TypeScript 2.0 was released, introducing several features, including the ability for programmers to optionally enforce null safety,[22] to mitigate what's sometimes referred to as the billion-dollar mistake.
TypeScript 3.0 was released on 30 July 2018,[23] bringing many language additions like tuples in rest parameters and spread expressions, rest parameters with tuple types, generic rest parameters and so on.[24]
TypeScript 4.0 was released on 20 August 2020.[25] While 4.0 did not introduce any breaking changes, it added language features such as Custom JSX Factories and Variadic Tuple Types.
TypeScript 5.0 was released on 16 March 2023 and included support for decorators.[26]
TypeScript originated from the shortcomings of JavaScript for the development of large-scale applications both at Microsoft and among their external customers.[27] Challenges with dealing with complex JavaScript code led to demand for custom tooling to ease developing of components in the language.[28]
Developers sought a solution that would not break compatibility with the ECMAScript standard and its ecosystem, so a compiler was developed to transform a superset of JavaScript with type annotations and classes (TypeScript files) back into vanilla ECMAScript 5 code. TypeScript classes were based on the then-proposed ECMAScript 6 class specification to make writing prototypal inheritance less verbose and error-prone, and type annotations enabled IntelliSense and improved tooling.
TypeScript adds the following syntax extensions to JavaScript:
Syntactically, TypeScript is very similar to JScript .NET, another Microsoft implementation of the ECMA-262 language standard that added support for static typing and classical object-oriented language features such as classes, inheritance, interfaces, and namespaces. Other inspirations include Java and C#.
TypeScript provides static typing through type annotations to enable type checking at compile time.
Primitive types are annotated using all-lowercase types, such as number, boolean, bigint, and string. These types are distinct from their boxed counterparts (Number, Boolean, etc), which cannot have operations performed from values directly (a Number and number cannot be added). There are additionally undefined and null types for their respective values.
All other non-primitive types are annotated using their class name, such as Error. Arrays can be written in two different ways which are both syntactically the same: the generic-based syntax Array<T> and a shorthand with T[].
Additional built-in data types are tuples, unions, never and any:
[type1, type2, ..., typeN].| symbol (string | number).never type is used when a given type should be impossible to create, which is useful for filtering mapped types.any supports the same operations as a value in JavaScript and minimal static type checking is performed,[30] which makes it suitable for weakly or dynamically-typed structures. This is generally discouraged practice and should be avoided when possible.[31]Type annotations can be exported to a separate declarations file to make type information available for TypeScript scripts using types already compiled into JavaScript. Annotations can be declared for an existing JavaScript library, as has been done for Node.js and jQuery.
The TypeScript compiler makes use of type inference when types are not given. For example, the add method in the code above would be inferred as returning a number even if no return type annotation had been provided. This is based on the static types of left and right being numbers, and the compiler's knowledge that the result of adding two numbers is always a number.
If no type can be inferred because of lack of declarations (such as in a JavaScript module without types), then it defaults to the dynamic any type. Additional module types can be provided using a .d.ts declaration file using the declare module "moduleName" syntax.
When a TypeScript script gets compiled, there is an option to generate a declaration file (with the extension .d.ts) that functions as an interface to the components in the compiled JavaScript. In the process, the compiler strips away all function and method bodies and preserves only the signatures of the types that are exported. The resulting declaration file can then be used to describe the exported virtual TypeScript types of a JavaScript library or module when a third-party developer consumes it from TypeScript.
The concept of declaration files is analogous to the concept of header files found in C/C++.
Type declaration files can be written by hand for existing JavaScript libraries, as has been done for jQuery and Node.js.
Large collections of declaration files for popular JavaScript libraries are hosted on GitHub in DefinitelyTyped.
See main article: Generic programming.
TypeScript supports generic programming using a syntax similar to Java.[32] The following is an example of the identity function.[33]
TypeScript uses the same annotation style for class methods and fields as for functions and variables respectively. Compared with vanilla JavaScript classes, a TypeScript class can also implement an interface through the implements keyword, use generic parameters similarly to Java, and specify public and private fields.
TypeScript distinguishes between modules and namespaces. Both features in TypeScript support encapsulation of classes, interfaces, functions and variables into containers. Namespaces (formerly internal modules) utilize JavaScript immediately-invoked function expressions to encapsulate code, whereas modules (formerly external modules) use existing JavaScript library patterns (CommonJS or ES Modules).[34]
See main article: JavaScript. As TypeScript is simply a superset of JavaScript, existing JavaScript can be quickly adapted to TypeScript and TypeScript program can seamlessly consume JavaScript. The compiler can target all ECMAScript versions versions 5 and above, transpiling modern features like classes and arrow functions to their older counterparts.
With TypeScript, it is possible to use existing JavaScript code, incorporate popular JavaScript libraries, and call TypeScript-generated code from other JavaScript.[35] Type declarations for these libraries are usually provided with the source code but can be declared or installed separately if needed.
The TypeScript compiler, named tsc, is written in TypeScript. As a result, it can be compiled into regular JavaScript and can then be executed in any JavaScript engine (e.g. a browser). The compiler package comes bundled with a script host that can execute the compiler. It is also available as a Node.js package that uses Node.js as a host.
The compiler can "target" a particular edition of ECMAScript (such as ES5 for legacy browser compatibility), but by default compiles for the latest standards.
See main article: Build automation. Using plug-ins, TypeScript can be integrated with build automation tools, including Grunt (grunt-ts[41]), Apache Maven (TypeScript Maven Plugin[42]), Gulp (gulp-typescript[43]) and Gradle (TypeScript Gradle Plugin[44]).
TSLint[45] scans TypeScript code for conformance to a set of standards and guidelines. ESLint, a standard JavaScript linter, also provided some support for TypeScript via community plugins. However, ESLint's inability to leverage TypeScript's language services precluded certain forms of semantic linting and program-wide analysis.[46] In early 2019, the TSLint team announced the linter's deprecation in favor of typescript-eslint, a joint effort of the TSLint, ESLint and TypeScript teams to consolidate linting under the ESLint umbrella for improved performance, community unity and developer accessibility.[47]
CodeDOM[48] provides types that represent common types of source code elements, which will be transformed to data types, classes and statements etc. of a programming language through a CodeDOMProvider.[49] Programmers use CodeDOM and a CodeDOM provider to construct a code generator that generates codes for an application domain.TypeScript CodeDOM Provider[50] generates TypeScript codes according to a CodeDOM.
| Version number | Release date | Significant changes | |
|---|---|---|---|
| 0.8 | |||
| 0.9 | |||
| 1.0 | |||
| 1.1 | performance improvements | ||
| 1.3 | protected modifier, tuple types | ||
| 1.4 | union types, let and const declarations, template strings, type guards, type aliases | ||
| 1.5 | ES6 modules, namespace keyword, for..of support, decorators | ||
| 1.6 | JSX support, intersection types, local type declarations, abstract classes and methods, user-defined type guard functions | ||
| 1.7 | async and await support, | ||
| 1.8 | constraints generics, control flow analysis errors, string literal types, allowJs | ||
| 2.0 | null- and undefined-aware types, control flow based type analysis, discriminated union types, never type, readonly keyword, type of this for functions | ||
| 2.1 | keyof and lookup types, mapped types, object spread and rest, | ||
| 2.2 | mix-in classes, object type, | ||
| 2.3 | async iteration, generic parameter defaults, strict option | ||
| 2.4 | dynamic import expressions, string enums, improved inference for generics, strict contravariance for callback parameters | ||
| 2.5 | optional catch clause variables | ||
| 2.6 | strict function types | ||
| 2.7 | constant-named properties, fixed-length tuples | ||
| 2.8 | conditional types, improved keyof with intersection types | ||
| 2.9 | support for symbols and numeric literals in keyof and mapped object types | ||
| 3.0 | project references, extracting and spreading parameter lists with tuples | ||
| 3.1 | mappable tuple and array types | ||
| 3.2 | stricter checking for bind, call, and apply | ||
| 3.3 | relaxed rules on methods of union types, incremental builds for composite projects | ||
| 3.4 | faster incremental builds, type inference from generic functions, readonly modifier for arrays, const assertions, type-checking global this | ||
| 3.5 | faster incremental builds, omit helper type, improved excess property checks in union types, smarter union type checking | ||
| 3.6 | Stricter generators, more accurate array spread, better Unicode support for identifiers | ||
| 3.7 | Optional chaining, nullish coalescing | ||
| 3.8 | Type-only imports and exports, ECMAScript private fields, top-level await | ||
| 3.9 | Improvements in inference, speed improvements | ||
| 4.0 | Variadic tuple types, labeled tuple elements | ||
| 4.1 | Template literal types, key remapping in mapped types, recursive conditional types | ||
| 4.2 | Smarter type alias preservation, leading/middle rest elements in tuple types, stricter checks for the in operator, abstract construct signatures | ||
| 4.3 | Separate write types on properties, override and the --noImplicitOverride flag, template string type improvements | ||
| 4.4 | Control flow analysis of aliased conditions and discriminants, symbol and template string pattern index signatures | ||
| 4.5 | Type and promise improvements, supporting lib from node_modules, template string types as discriminants, and es2022 module | ||
| 4.6 | Type inference and checks improvements, support for ES2022 target, better ECMAScript handling | ||
| 4.7 | Support for ES modules, instantiation expressions, variance annotations for type parameters, better control-flow checks and type check improvements | ||
| 4.8 | Intersection and union types improvements, better type inference | ||
| 4.9 | satisfies operator, auto-accessors in classes (proposal), improvements in type narrowing and checks | ||
| 5.0 | ES decorators (proposal), type inference improvements, bundler module resolution mode, speed and size optimizations | ||
| 5.1 | Easier implicit returns for undefined and unrelated types for getters and setters | ||
| 5.2 | using declarations and explicit resource management, decorator metadata and named and anonymous tuple elements | ||
| 5.3 | Improved type narrowing, correctness checks and performance optimizations | ||
| 5.4 | 6 March 2024 | Object.groupBy and Map.groupBy support | |
| 5.5 | 20 June 2024 | Inferred Type Predicates, Regular Expression Syntax Checking, and Type Imports in JSDoc | |
| 5.6 | 9 September 2024 | Advanced type inference, variadic tuple enhancements, partial module declarations. |