New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Transformer not working since RN 0.43 #2
Comments
Is there any update on this? |
a workaround is using webpack with haul instead of rn packager |
@rodrigopivi ah, neat! I haven't seen haul. I'll look into that. For now I removed the custom transformer. I'll set up webpack as soon as I get annoyed because I don't have source maps. Haha Thanks! |
I don't have time to fix this myself right now, but in case anybody right now wants to work on it, it's because of an API break in |
Relevant RN commit: facebook/react-native@a4d7a78#diff-4676ea0b3c55c65c3929aa993144f07f |
I fix by your way. it works without error, but it map to a wrong line. |
Are there any updates on this? |
TS debugging in RN likely won't work at all until this React Native issue with transformers is resolved. |
Does anyone have a workaround for this yet? How is it that this has been broken for so long, and react-native hasn't fixed it yet? |
The code taps into the internals of react-native which obviously has changed in the subsequent versions, so the breakage of this little utility is kind of inevitable. |
After updating to RN 0.43, when i try to start the RN packager using a custom transformer like:
I get a error at the packager output:
The text was updated successfully, but these errors were encountered: