David Sheldrick

@karsens I think you will save some time if you use this library still, however I know of one team who have tried out babel 7 successfully, with the caveat...

Good point. My thinking behind recommending the rn-cli.config.js file is that there are a bunch of ways to run the packager. e.g. `react-native run-android`, `react-native run-ios`, `react-native bundle`, etc. All...

> Sadly-Typed Components :joy: Not sure how to automate this. I think it would require a new TypeScript module resolution strategy which extends `node`. I imagine the MS folks would...

@liamjones I found some discussion here: https://github.com/Microsoft/TypeScript/issues/8328

Thansk for the report! Can you post your tsconfig file?

Awesome, thanks! As a first step, can you try this: ```diff { "compilerOptions": { "target": "es2015", + "module": "es2015", "jsx": "react", "baseUrl": "./src", "noEmit": true, "noImplicitAny": false, "strictNullChecks": false, "allowSyntheticDefaultImports":...

Hmm looks like they added a `plugins` field to the transform props https://github.com/facebook/metro/blob/d894a24f4352004df73be6c9ed24f4de7d4da341/packages/metro/src/reactNativeTransformer.js#L154 Maybe passing that along will help. (I'll try this out later)

I updated the readme

It should Just Work, so maybe there are some issues. 1. Are the lines correct at dev time? 2. Which versions of everything are you running?

Ah, yes. Makes sense. The issue causing inaccurate maps for production bundles was fixed in RN 0.52. Are you able to update? On Tue, 20 Feb 2018, 15:52 Henrik Raitasola,...