17
TypeScript: Getting Started
TypeScript has taken the development world by storm. No wonder it has over 15 million weekly downloads on npm. But what is TypeScript, and what do you need to know about it?
In this article, I am going answer those questions. By the end you'll have a grasp of the following:
- What TypeScript is
- Main pillars of TypeScript
- Main features of TypeScript
- Why you should use TypeScript
- TypeScript basics to get you started
First, let's address the elephant in the room.
TypeScript is a programming language built and maintained by Microsoft.
It is a superset of JavaScript that adds strong type checking and is compiled into plain JavaScript code.
Being a superset means that TypeScript has all the features of JavaScript as well as some additional features.
TypeScript comes with features such as better development-time tooling, static code analysis, compile-time type checking, and code-level documentation.
Don't worry if you have no idea what any of this means. I'll explain all of it in this article.
All these features that come with TypeScript make it the perfect programming language for building large-scale JavaScript applications.
TypeScript is built upon three main pillars – namely the language, the compiler, and the language service.
This consists of the syntax, keywords, and type annotations of TypeScript.
TypeScript syntax is similar to but not the same as JavaScript syntax.
The compiler is responsible for compiling Typescript code into JavaScript.
In reality, what happens is not actually compiling but transpiling.
Compiling means that source code is transformed from a human-readable format to a machine-readable format, whereas transpiling is transforming source code from one human-readable format to another human-readable format.
The TypeScript compiler is also responsible for erasing any information related to types at compile time.
Types are not valid features in JavaScript. And since TypeScript has to be compiled to plain JavaScript, anything related to types has to be erased before it can become valid JavaScript ready to be executed by the browser.
The TypeScript compiler also performs code analysis. It emits errors and warnings if there's reason to do so.
The language service is responsible for collecting type information from the source code.
This information can then be used by development tools to provide IntelliSense, type hints, and refactoring alternatives.
Type annotation simply means assigning a type to a variable or function.
const birthdayGreeter = (name: string, age: number): string => {
return `Happy birthday ${name}, you are now ${age} years old!`;
};
const birthdayHero = "Jane User";
const age = 22;
console.log(birthdayGreeter(birthdayHero, 22));In the above example, we define a function that accepts two parameters name and age. We assign name to the type string age to the type number
We can also assign types to the return value of a function. In this case, our function returns a value of the type string
const birthdayGreeter = (name: string, age: number): string => { };
Typescript would yield an error if we passed in arguments of different types than ones we expectTypeScript is a structurally typed language meaning that if two elements have corresponding and identical features then they are considered to be of the same type.
The TypeScript compiler can attempt to infer the type information if there is no specific type assigned. This means that TypeScript can assign a type to a variable or function based on its initial values or usage.
Type inference usually happens when you initialize variables, set default values, and determe function return types
const platform = 'freeCodeCamp';
const add = (a: number, b: number) => a + bThe variable platform in the above example is assigned the type string even though we didn't explicitly do so and the return value of the function add is inferred the type number.
TypeScript removes the type system constructs during compilation:
Input
let x: someType;Output
let x;This reduces the overall errors in your code because TS will warn you when you wrongfully use a certain type.
It also reduces runtime errors and because of static code analysis, TypeScript will throw warnings about typos and such. So this means fewer errors which could potentially mean less testing.
Type annotations help us to understand what type of arguments a function expects, for example, and what it returns.
This makes code more readable and makes it easier for others and for us to understand what the code is supposed to do.
Another advantage of TypeScript is that IDEs can provide more specific and smarter IntelliSense when they know exactly what types of data you are processing.
Let's begin by installing the TypeScript package. Here we have two options: we can either install it globally so we can use it on any project in the system, or we can install it to use on the specific project we're working on.
You can install TypeScript globally by running this command:
npm install -g typescriptIf you don't wish to install globally you can just run this:
npm install --save-dev typescriptIn the local installation, TypeScript is installed as a Dev-dependency because we use it for development. It has to first compile to JavaScript before it can be used in production. The browser can't execute TypeScript.
After installing TypeScript, we need to initiate a new project. You can do that by running the following command:
tsc --initThis command initiates a new tsconfig.json file in the root directory of the project. This config file comes with all the configuration options we have for using TypeScript in a project.
All the compile options for a particular project can be specified in the tsconfig.json file under the compileOptions key.
The file comes with some config options by default but you can add more options to the project as needed. You can comment out or delete unused compiler options.
Typescript comes built-in with all the primitive types in JavaScript like string, number, and boolean.
The types can then be assigned to variables to specify what data type should be assigned to the variable. This is called type annotation.
const myName: string = 'Joel';
const myAge: number = 99;TypeScript annotations are not always necessary because TypeScript automatically infers the type of a variable based on its initial value or usage. Therefore the following would also be valid TypeScript code:
// myName is inferred type 'string'
const myName = 'Jonathan';To specify the type of an array you can use the syntax string[] or number[]. This effectively means 'array of strings or array of numbers'.
You'll also see people use the syntax Array<number> or Array<string> which means the same thing.
Union types allow us to define several types that may be assigned to a variable. For this, we use a pipe | to specify the various types.
const someValue: number | string = value;By default null | undefined can be assigned to any variable but TypeScript comes with the strictNullChecks compiler option which does not allow assigning both to a variable.
Functions can also receive type annotations. However, with TypeScript functions, they can only receive the specified parameters. Nothing more nothing less.
function introduction(name: string, age: number): string {
return `Hello, my name is ${name} and I'm {age} years old`
}Function parameters receive normal type annotation.
TypeScript functions must also specify the return data type. In the case where a function returns nothing, we can use void type as the return data type.
We can also use the ? operator to specify parameters that are optional. In this case, Typescript won't complain if the parameter is not passed on the function call.
We can also assign default values to parameters just like we would in normal JavaScript.
const introduction = (name: string, age: number, job?: string = 'developer'): string => `Hello, my name is ${name} and I'm ${age} years old. I work as a ${job}`Notice that in this example I used the JavaScript arrow function syntax and specified that the job parameter is optional and assigned a default value 'developer' to it.
In TypeScript, every variable whose type cannot be inferred becomes implicitly the type any.
Any is typically a wild card type that literally means 'whatever type'. We can also explicitly assign the type any to a variable.
However, any typings are usually considered to be problematic.
Typescript comes with the noImplicitAny compiler option which raises an error when we assign the type any to a variable or expression.
TypeScript offers a way for us to define and use our own types for inputs. Here we can describe the exact type that is acceptable for a particular input.
We can use the type keyword to define our own types.
type Operator = 'multiply' | 'add' | 'divide';Now the Operator type can accept either of the values. Notice how we use the OR operator | to create a union type. In this case, any variable assigned the type Operator can accept any of the three values.
Let's now use this knowledge to create a simple calculator program. A user can only enter one of three operations - add, multiply, or divide. If you want to, take a moment and try to attempt this then you come back and follow along.
Hopefully, you tried it on your own. The program may then look something like this:
type Operation = 'multiply' | 'add' | 'divide';
const calculator = (a: number, b:number, op: Operation): number => {
switch(op) {
case 'multiply':
return a * b;
case 'add':
return a + b;
case 'divide':
if (b === 0) return 'Can't divide by 0;
return a / b;
default:
return 'Operation unknow';
}
}Try to read the above code and see if you can figure out what is going on.
We can also create custom types using the interface keyword. Interfaces allow us to define the property and type of an object. An interface can have the ability to extend another interface.
interface Employee {
name: string,
title: string
}
interface Manager extends Employee {
meeting: (topic: string) => void
}Here we define an interface Employee which has two properties - name and title, both of which are of the type string.
We then use this interface to create another interface Manager which has the same properties as the Employee interface but with a meeting method.
At the outset, I mentioned that Typescript is a structurally typed language. This means that if an element has the same properties as another, they're both of the same types.
The same is true with interfaces. If an object has the properties of an interface then it has the type of the interface. Such an object can have additional properties as long as some properties match those of the interface.
We can now use our defined interface such as:
const newEmployee: Employee = {
name: 'Joel',
title: 'FrontEnd Developer'
}So far we've seen that we can create our own types using the type and interface keywords. But, what is the difference between the two?
The most notable difference is that defining multiple interfaces with the same name will result in a merged interface. On the other hand, defining multiple types with the same name will result in an error indicating that the name is already declared.
Typescript has a lot of features that can't simply be exhausted in this article. I just highlighted a few of the features that may be helpful to understand in order to get started working with it.
You can learn more about Typescript by reading the documentation.
17