Using TypeScript with React Native
TypeScript is a language which extends JavaScript by adding type definitions, much like Flow. While React Native is built in Flow, it supports both TypeScript and Flow by default.
Getting Started with TypeScript
If you're starting a new project, there are a few different ways to get started. You can use the TypeScript template:
Note If the above command is failing, you may have old version of
react-native
orreact-native-cli
installed globally on your pc. Try uninstalling the cli and run the cli usingnpx
.
You can use Expo which has two TypeScript templates:
Or you could use Ignite, which also has a TypeScript template:
Adding TypeScript to an Existing Project
- Add TypeScript and the types for React Native and Jest to your project.
- Add a TypeScript config file. Create a
tsconfig.json
in the root of your project:
- Create a
jest.config.js
file to configure Jest to use TypeScript
- Rename a JavaScript file to be
*.tsx
You should leave the
./index.js
entrypoint file as it is otherwise you may run into an issue when it comes to bundling a production build.
- Run
yarn tsc
to type-check your new TypeScript files.
How TypeScript and React Native works
Out of the box, transforming your files to JavaScript works via the same Babel infrastructure as a non-TypeScript React Native project. We recommend that you use the TypeScript compiler only for type checking. If you have existing TypeScript code being ported to React Native, there are one or two caveats to using Babel instead of TypeScript.
What does React Native + TypeScript look like
You can provide an interface for a React Component's Props and State via React.Component<Props, State>
which will provide type-checking and editor auto-completing when working with that component in JSX.
You can explore the syntax more in the TypeScript playground.
Where to Find Useful Advice
- TypeScript Handbook
- React's documentation on TypeScript
- React + TypeScript Cheatsheets has a good overview on how to use React with TypeScript
Using Custom Path Aliases with TypeScript
To use custom path aliases with TypeScript, you need to set the path aliases to work from both Babel and TypeScript. Here's how:
- Edit your
tsconfig.json
to have your custom path mappings. Set anything in the root ofsrc
to be available with no preceding path reference, and allow any test file to be accessed by usingtest/File.tsx
:
- Configure the Babel side done by adding a new dependency,
babel-plugin-module-resolver
:
- Finally, configure your
babel.config.js
(note that the syntax for yourbabel.config.js
is different from yourtsconfig.json
):