TypeScript

Jump to navigation Jump to search

"Typescript" redirects here. For a typewritten manuscript, see Manuscript.

TypeScript is an open-source programming language developed and maintained by Microsoft. It is a strict syntactical superset of JavaScript, and adds optional static typing to the language.

TypeScript is designed for development of large applications and transcompiles to JavaScript.[5] As TypeScript is a superset of JavaScript, existing JavaScript programs are also valid TypeScript programs. TypeScript may be used to develop JavaScript applications for both client-side and server-side (Node.js) execution.

For the transcompilation process, there are multiple options available. You can use the default TypeScript Checker to do so[6], or you can rely on Babel for converting your TypeScript to JavaScript[7]

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 basic modules are also available, allowing development of Node.js programs within TypeScript.[8]

The TypeScript compiler is itself written in TypeScript and compiled to JavaScript. It is licensed under the Apache 2 License.

TypeScript is included as a first-class programming language in Microsoft Visual Studio 2013 Update 2 and later, beside C# and other Microsoft languages.[9] An official extension allows Visual Studio 2012 to support TypeScript as well.[10]

Anders Hejlsberg, lead architect of C# and creator of Delphi and Turbo Pascal, has worked on the development of TypeScript.[11][12][13][14]

Contents

History

TypeScript was first made public in October 2012 (at version 0.8), after two years of internal development at Microsoft.[15][16] Soon after the announcement, 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 OS X at that time.[17][18] Today there is support in other IDEs, particularly in Eclipse, via a plug-in contributed by Palantir Technologies.[19][20] Various text editors, including Emacs, Vim, Sublime, Webstorm, Atom[21] and Microsoft's own Visual Studio Code also support TypeScript.[22]

TypeScript 0.9, released in 2013, added support for generics.[23] TypeScript 1.0 was released at Microsoft's Build developer conference in 2014.[24] Visual Studio 2013 Update 2 provides built-in support for TypeScript.[25]

In July 2014, the development team announced a new TypeScript compiler, claiming 5× performance gains. Simultaneously, the source code, which was initially hosted on CodePlex, was moved to GitHub.[26]

On 22 September 2016, TypeScript 2.0 was released; it introduced several features, including the ability for programmers to optionally prevent variables from being assigned null values,[27] sometimes referred to as the billion-dollar mistake.

Language design

TypeScript originated from the shortcomings of JavaScript for the development of large-scale applications both at Microsoft and among their external customers.[28] Challenges with dealing with complex JavaScript code led to demand for custom tooling to ease developing of components in the language.[29]

TypeScript developers sought a solution that would not break compatibility with the standard and its cross-platform support. Knowing that the current ECMAScript standard proposal promised future support for class-based programming, TypeScript was based on that proposal. That led to a JavaScript compiler with a set of syntactical language extensions, a superset based on the proposal, that transforms the extensions into regular JavaScript. In this sense TypeScript was a preview of what to expect of ECMAScript 2015. A unique aspect not in the proposal, but added to TypeScript, is optional static typing[30] that enables static language analysis, which facilitates tooling and IDE support.

ECMAScript 2015 support

Main article: ECMAScript § 6th Edition - ECMAScript 2015

TypeScript adds support for features such as classes, modules, and an arrow function syntax as defined in the ECMAScript 2015 standard.

Language features

TypeScript is a language extension that adds features to ECMAScript 6. Additional features include:

The following features are backported from ECMAScript 2015:

• Classes
• Modules[31]
• Abbreviated "arrow" syntax for anonymous functions
• Optional parameters and default parameters

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.

Compatibility with JavaScript

TypeScript is a strict superset of ECMAScript 2015, which is itself a superset of ECMAScript 5, commonly referred to as JavaScript.[32] As such, a JavaScript program is also a valid TypeScript program, and a TypeScript program can seamlessly consume JavaScript. By default the compiler targets ECMAScript 5, the current prevailing standard, but is also able to generate constructs used in ECMAScript 3 or 2015.

With TypeScript, it is possible to use existing JavaScript code, incorporate popular JavaScript libraries, and call TypeScript-generated code from other JavaScript.[33] Type declarations for these libraries are provided with the source code.

Type annotations

TypeScript provides static typing through type annotations to enable type checking at compile time. This is optional and can be ignored to use the regular dynamic typing of JavaScript.

function add(left: number, right: number): number {
 return left + right;
}

The annotations for the primitive types are number, boolean and string. Weakly- or dynamically-typed structures are of type any.

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 to infer types 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. However, explicitly declaring the return type allows the compiler to verify correctness.

If no type can be inferred because of lack of declarations, then it defaults to the dynamic any type. A value of the any type supports the same operations as a value in JavaScript and minimal static type checking is performed for operations on any values.[34]

Declaration files

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 file found in C/C++.

declare namespace arithmetics {
    add(left: number, right: number): number;
    subtract(left: number, right: number): number;
    multiply(left: number, right: number): number;
    divide(left: number, right: number): number;
}

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.

Classes

TypeScript supports ECMAScript 2015 classes that integrate the optional type annotations support.

class Person {
    private name: string;
    private age: number;
    private salary: number;

    constructor(name: string, age: number, salary: number) {
        this.name = name;
        this.age = age;
        this.salary = salary;
    }

    toString(): string {
        return `${this.name} (${this.age}) (${this.salary})`; // As of version 1.4
    }
}

Generics

TypeScript supports generic programming.[35]

Modules and namespaces

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 immediately-invoked function expression of JavaScript to encapsulate code, whereas modules (formerly external modules) leverage JavaScript library patterns to do so (AMD or CommonJS).[36]

Compiler

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.

There is also an alpha version of a client-side compiler in JavaScript, which executes TypeScript code on the fly, upon page load.[37]

The current version of the compiler supports ECMAScript 5 by default. An option is allowed to target ECMAScript 2015 to make use of language features exclusive to that version (e.g. generators). Classes, despite being part of the ECMAScript 2015 standard, are available in both modes.

IDE and editor support

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.

Release history

Version number Release date Significant changes 0.8 1 October 2012 ( ) 0.9 18 June 2013 ( ) 1.1 6 October 2014 ( ) performance improvements 1.3 12 November 2014 ( )

protected modifier, tuple types 1.4 20 January 2015 ( ) union types,

let and

const declarations, template strings, type guards, type aliases 1.5 20 July 2015 ( ) ES6 modules,

namespace keyword,

for..of support, decorators 1.6 16 September 2015 ( ) JSX support, intersection types, local type declarations, abstract classes and methods, user-defined type guard functions 1.7 30 November 2015 ( )

async and

await support, 1.8 22 February 2016 ( ) constraints generics, control flow analysis errors, string literal types,

allowJs 2.0 22 September 2016 ( ) null- and undefined-aware types, control flow based type analysis, discriminated union types,

never type,

readonly keyword, type of

this for functions 2.1 8 November 2016 ( )

keyof and lookup types, mapped types, object spread and rest, 2.2 22 February 2017 ( ) mix-in classes,

object type, 2.3 27 April 2017 ( )

async iteration, generic parameter defaults, strict option 2.4 27 June 2017 ( ) dynamic import expressions, string enums, improved inference for generics, strict contravariance for callback parameters 2.5 31 August 2017 ( ) optional catch clause variables 2.6 31 October 2017 ( ) strict function types 2.7 31 January 2018 ( ) constant-named properties, fixed length tuples 2.8 27 March 2018 ( ) conditional types, improved

keyof with intersection types 2.9 14 May 2018 ( ) support for symbols and numeric literals in keyof and mapped object types 3.0 30 July 2018 ( ) project references, extracting and spreading parameter lists with tuples 3.1 27 September 2018 ( ) mappable tuple and array types 3.2 30 November 2018 ( ) stricter checking for bind, call, and apply 3.3 31 January 2019 ( ) relaxed rules on methods of union types, incremental builds for composite projects

See also

References

Citations

Sources

‏Source en.wikipedia.org