Ignite TypeScript Boilerplate
This is a work in progress, but is enough to get started with React Native development in TypeScript.
The great taste of Ignite, now in TypeScript
A port of the Ignite IR Boilerplate to TypeScript.
- React Native 0.51.0 (but you can change this if you want to experiment)
- React Navigation
- Redux Sagas
- And more!
When you've installed the Ignite CLI, you can get started with this boilerplate like this:
ignite new MyLatestCreation --b ignite-typescript-boilerplate
You can also change the React Native version, just keep in mind, we may not have tested this just yet.
ignite new MyLatestCreation --b ignite-typescript-boilerplate --react-native-version 0.46.0-rc.2
By default we'll ask you some questions during install as to which features you'd like. If you just want them all, you can skip the questions:
ignite new MyLatestCreation --b ignite-typescript-boilerplate --max
If you want very few of these extras:
ignite new MyLatestCreation --b ignite-typescript-boilerplate --min
Using TypeScript with React Native
Thanks to the beauty of react-native-typescript-transformer, we can seamlessly use TypeScript in our React Native project. Source maps and hot reloading all work just like you would expect.
tslint to enforce coding style, with rules based on Palantir's tslint-react,
and a few changes to accommodate some Ignite quirks. If you install a plugin, your editor can probably automatically fix problems.
In VS Code, set
"tslint.autoFixOnSave": true in your
workspace settings. You can run the linter from the command line.
npm run lint runs the linter, while
npm run fixcode tries to autofix problems.
App folder is where most of the goodies are found in an Ignite app. Let's walk through them in more detail. Start with
Containers/App.tsx (described below) and work your way down the walkthrough in order.
Containers are (mostly) full screens, although they can be sections of screens or application containers.
App.tsx- your main application. We create a Redux store and configure it here
RootContainer.tsx- main view of your application. Contains your status bar and navigation component
LaunchScreen.tsx- this is the first screen shown in your application. It's loaded into the Navigation component
LoginScreen.tsx- an example login screen. Read the comments in there to learn more!
Your primary and other navigation components reside here.
AppNavigation.tsx- loads in your initial screen and creates your menu(s) in a StackNavigation
Styles- styling for the navigation
React components go here. We generate these as stateless functional components by default, as recommended by the React team.
Storybook has been setup to show off components in the different states. Storybook is a great way to develop and test components outside of use in your app. Simply run
npm run storybook to get started. All stores are contained in the
*.story.tsx files along side the components.
Styling themes used throughout your app styles.
ApplicationStyles.ts- app-wide styles
Colors.ts- defined colors for your app
Fonts.ts- defined fonts for your app
Images.ts- loads and caches images used in your app
Metrics.ts- useful measurements of things like navBarHeight
Initialize and configure things here.
AppConfig.ts- simple React Native configuration here
DebugConfig.js- define how you want your debug environment to act. This is a .js file because that's what Ignite expects to find.
ReactotronConfig.ts- configures Reactotron in your project (Note: this will be extracted into a plugin in the future)
Contains json files that mimic API responses for quicker development. These are used by the
Services/FixtureApi.ts object to mock API responses.
Contains a preconfigured Redux and Redux-Sagas setup. Review each file carefully to see how Redux interacts with your application. You will find these in the Reducers and Sagas folders. We use typesafe-actions to get lovely
type checking of our reducers and actions. Take a look at
Lib/ReduxHelpers.ts for some extra functions that
we use to make them more Ignite-y.
Contains your API service and other important utilities for your application.
Api.tsx- main API service, giving you an interface to communicate with your back end
ExamplesRegistry.tsx- lets you view component and Ignite plugin examples in your app
FixtureApi.tsx- mocks your API service, making it faster to develop early on in your app
We recommend using this folder for modules that can be extracted into their own NPM packages at some point.
Contains actual images (usually png) used in your application.
Helpers for transforming data between API and your application and vice versa. An example is provided that you can look at to see how it works.
We create Jest tests alongside the components, reducers and sagas. Currently you need to enable this by editing
ignite/ignite.json and adding
Currently, the following code generation commands work properly:
ignite generate component MyComponent- generates a stateless functional component.
ignite generate container MyContainer- generates a Redux-connected React.Component, with state and view lifecycle.
ignite generate screen MyScreen- generates a Redux-connected React.Component, with state, view lifecycle and react-navigation.
ignite generate reducers MyNew- generates a set of Redux reducers.
ignite generate saga MySaga- generates a Redux Saga
A comprehensive guide to best practice with TypeScript in React is the React Redux TypeScript Guide, which covers a lot more than just Redux. We have adopted a lot of the patterns from this. The
typesafe-actions library that we use was created by @piotrwitek, the author of the guide.
Microsoft created TypeScript React Native Starter, which includes a walkthrough on switching projects to TypeScript.
React TypeScript Tutorial is React rather than React Native, but has useful guides.