David Sheldrick

https://github.com/ds300/react-native-typescript-transformer/issues/11 **tldr** react-native used to have a spot in the production build pipeline where input source maps were ignored. That issue was resolved as a side effect of a big...

I can't think of anything that you could do that might solve the problem in 'userland'. If the source maps line up during development but not in production releases, then...

Sorry I haven't looked into this issue

Yes, thanks for the reminder! First I'll update the transformer to be able to run without babel if TS is >= 2.7

update on this: Last night I ripped out the babel transform, and ran in to this issue: https://github.com/Microsoft/TypeScript/issues/21621 Once that bug is solved I'll be happy to release react-native-typescript-transformer 2.0...

So so close! :D Just need to wait for TS 2.9 to drop. Should be any day now 🤞

https://twitter.com/typescriptlang/status/1002230349521338368?s=19 🎊💃🕺🎉 Unfortunately I'm busy with non-tech stuff for a few days, but I'll work on a new release ASAP.

Hey Axel :-) I'd recommend using [ts-jest](https://github.com/kulshekhar/ts-jest). It is more mature than `lozinsky/typescript-babel-jest`. It makes sense to use `react-native-typescript-transformer` with Jest to get the consistency between test and bundle code....

Hey @GeeWee That would would be awesome. Any ideas about how this could be done? It has been a long while since I looked at the ts-jest code.

@vovkasm This is cool! Thanks for sharing :) I still haven't heard of anyone having problems with `ts-jest` (specifically caused by differences between it's transformer and react-native-typescript-transformer), and it solves...