orta / systems-theory

React Native in TypeScript that feels good

React Native in TypeScript

This repo aims to take a vanilla JS React Native app, and transform it into a working, awesome, TypeScript one.

It is a sibling project to relational-theory which strives to build a similar system but from a web perspective.

We build specifically for working with VS Code.

Aims:

• Components all have defined State / Props
• Hot Module Reloading on Save
• Source Mapping in debugging works
• Babel Transformations work for Relay
• Testing / Watcher mode in Jest is 👍
• Source Mapping works in Tests

Why TypeScript?

There'll probably be a longer write up on the Artsy blog once we've got this stuff in production. However, the TLDR is that TypeScript provides more mature tooling, with the accessibility of being built in JavaScript.

References

Code:

• mrpatiwi/ReactNativeTS
• philikon/ReactNativify
• frogcjn's debugging gist

Text:

• Microsoft/TypeScript/#11441
• reactnative.tools
• react-weekly
• raygun.com

systems-theory's Issues

Question about transformer.js’ filetype inference.

Why do you check the sourceCode data here rather than the filename one? Shouldn’t checking the filename be faster?

React Packager does not recognize *.ts files

As seen here: https://github.com/facebook/react-native/blob/master/packager/react-packager/src/node-haste/DependencyGraph/ResolutionRequest.js#L417-L436

Noted from https://gist.github.com/frogcjn/3bb47ce01a5168d8cd570a46cc71bb02

Possible work around?

Use *.js files for TypeScript

This one is tricky, but may be feasible via a custom compiler inside a rn-cli.config.js.