❮ Back to index

Flow and TypeScript part 2: TypeScript

Writing proposals? Try Proppy, our new product!

Reading time: ~10 minutes.

Continuing from the first part that introduced Flow, we are now going to have a look at TypeScript.

TypeScript is a superset of JavaScript that compiles to several targets, including ES5 and ES6. The current version of TypeScript (1.6 at the time of writing) now supports JSX, which was the main blocker for most people using React.

One of the great advantages of TypeScript is DefinitelyTyped. This repo contains definitions for over a thousand JavaScript packages but more on that later.

We've implemented the same project once in Flow and once in TS. Find the repo here. Note that I have used TypeScript for a project before.

Converting a project to TypeScript

Moving a project to TypeScript is not as straightforward as it was for Flow.

There are a couple of steps and gotchas which I will explain on the way.

Build tools

Obviously you are going to need to configure your build tools to use TypeScript rather than what you were using before. In my case, I was using Webpack so I only had to replace eslint with tslint and add ts-loader to the mix.

As mentioned in the introduction, TypeScript can target ES5 or ES6. The advantage of targeting ES6 is that you can still use Babel to compile and benefit from webpack's hot module reload. For more information on how to do that, please read ES6 modules with TypeScript and webpack and have a look at the webpack config for a practical example.

Actual conversion

TypeScript uses a config file named tsconfig.json. Here's the one currently used by the example:

  "compilerOptions": {
    "target": "es6",
    "jsx": "react",
    "noImplicitAny": true,
    "sourceMap": true
  "exclude": ["node_modules", "gulpfile.js", "webpack.config.js", "server.js"]

When you are starting the conversion, you probably want to remove the "noImplicitAny": true, line since it would error if you have any missing type annotations, which is going to be the case pretty much everywhere.

You then need to rename all your .js files to .ts and .tsx. The .txs extension is needed if the file contains JSX.

Some gotchas and examples

While TypeScript intends to support most of ES6 and ES7 features, you will need to change some bits of your code. Here are the main ones I ran into and some cool TypeScript features.

Object destructuring assignment

It doesn't work in TypeScript (playground). Let's look at the combineReducers from redux for example:

const reducer = combineReducers({
  router: routerStateReducer,
// will need to be changed to
const reducer = combineReducers({
  router: routerStateReducer,
  lists: reducers.lists,
  cards: reducers.cards

Importing default

Importing the default from a ES6 module is different from the Babel one. For example in the case of React:

// will not work in typescript
import React from "react";
// will work in typescript
import * as React from "react";

Adding 3rd party definitions

Adding type definitions for your own app is great but if you are using 3rd party libraries without definitions for them you don't gain much confidence.

Thankfully we have DefinitelyTyped to save us. It's a git repo containing definitions for other a thousand JavaScript libraries. There is a tool called tsd to manage definitions but frankly, I don't use so many libraries that it's worth the hassle over manually copying files.

React PropTypes

Now that you have real types, you can delete all of the React PropTypes and add interfaces for your components props and state like in the following example:

interface IAddFormProps {
  placeholder: string;
  callback: (value: string) => void;

export class AddForm extends React.Component<IAddFormProps, {}>{...}

Those props will be checked at compile time rather than runtime and will fail if props are missing or have the wrong type.


TypeScript and React are working really well together!

The only issues we have encountered so far (and would love help to resolve!) are:

  • webpack building the previous version: adding an empty line and saving a file re-triggers a compilation but can be frustrating
  • no string enums: we want to keep human readable enum members but TypeScript only supports int enums

I remember trying TypeScript with ImmutableJS records months ago and giving up. With a more recent version of TypeScript, we now have both records working (they are used in the example repo if you are curious) and JSX.

Moving to TypeScript is definitely more involved than moving to Flow where you can easily do file by file. On the other hand, the TypeScript community is much bigger and definitions are widely available and you can integrate the tools directly in your pipeline, as opposed to running Flow outside of it. It also doesn't do much inference compared to Flow and need to explicitely type most of the things. For reference, it took us 3h to move one of the product we are working on to TypeScript (without the noImplicitAny: true yet) while adding Flow took us around 25 minutes. The typing provided by TypeScript was much more complete though and revealed 4 bugs in the codebase.

In terms of IDE support, TypeScript is probably better than Flow (with https://code.visualstudio.com/ for example) but in my PyCharm, both are good.

I think TypeScript is the best bet right now despite believing that the Flow approach is the best one. What is lacking for Flow to catchup is community and tooling.

As for us, we just merged our TypeScript branch and closed the Flow one.