@scott dukat issues are better to create indeed at
https://github.com/Kotlin/dukat/issues
don't be put off by the fact that many of ts2kt bugs are still there - in fact many of them were just migrated to just rechecked and be closed.
if any of "old" issues is still there - just ping in a comment to that task and I'll prioritise it.
no need to say that react-native is very important library and one problem that it turns out to be contributing to confusion that sometimes what else is in node_modules package affect how the rest of artifacts are resolved.
That said, sometimes in clean environment something is not reproducible why in real-life scenarios it does.
However from what I see for react-native the problem is actually under investigation and planned to 0.0.29 - I'll reintroduce milestones to the issues to make the process of bugfixes transparent