This quick start guide will teach you how to wire up TypeScript with [React](http://facebook.github.io/react/).

By the end, you'll have

* linting with [TSLint](https://github.com/palantir/tslint)

* state management with [Redux](https://github.com/reactjs/react-redux)

We assume that you're already using [Node.js](https://nodejs.org/) with [npm](https://www.npmjs.com/).

This is just a command-line utility to scaffold out new React projects.

Of note:

* `tslint.json` stores the settings that our linter, [TSLint](https://github.com/palantir/tslint), will use.

* `package.json` contains our dependencies, as well as some shortcuts for commands we'd like to run for testing, previewing, and deploying our app.

* `public` contains static assets like the HTML page we're planning to deploy to, or images. You can delete any file in this folder apart from `index.html`.

}

So in `src/components/Hello.tsx`, we'll add the following import.

However, React doesn't come with any facility for synchronizing data between your application.

As far as a React component is concerned, data flows down through its children through the props you specify on each element.

[Redux](http://redux.js.org) relies on synchronizing data through a centralized and immutable store of data, and updates to that data will trigger a re-render our application.

State is updated in an immutable fashion by sending explicit action messages which must be handled by functions called reducers.

Keeping state fully synchronized for any observers is done by simply marking state as observable.

As a nice bonus, the library is already written in TypeScript.

Generally Redux tends to see more widespread usage, so for the purposes of this tutorial, we'll focus on adding Redux;

however, you should feel encouraged to explore both.

It doesn't make sense to add Redux unless the state of our application changes.

and you should be good to go!

As a heads up, you may want to commit all your work before running an eject.