-
Notifications
You must be signed in to change notification settings - Fork 48
Note on allowSyntheticDefaultImports #47
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
Comments
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: microsoft/TypeScript#21621 Once that bug is solved I'll be happy to release react-native-typescript-transformer 2.0 which won't use babel at all and will only support React Native >= 0.52 wip branch over here: https://github.com/ds300/react-native-typescript-transformer/tree/no-babel |
Sounds good! |
@ds300 Looks like the issue is closed? So we are getting rid of babel now? :O |
So so close! :D Just need to wait for TS 2.9 to drop. Should be any day now 🤞 |
What a roller coaster.
You're killing me here David. |
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 @ds300 , how's the 2.0 coming along? Honestly I'm just unsure if I should set |
In readme it reads:
That issue is now closed so I guess the README should change too?
The text was updated successfully, but these errors were encountered: