-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
CLEANUP: Remove Flow Babel preset once the TS migration is done #20592
Comments
Job added to Upwork: https://www.upwork.com/jobs/~019322a03e0bf0ef98 |
Triggered auto assignment to @tjferriss ( |
this doesn't need C+ review un assigning @mananjadhav 🙇 |
This is an internal cleanup. PLEASE DO NOT POST PROPOSALS |
this is monthly issue removing the daily label |
the migration is still going on |
the migration is still going on |
TS migration is still going on |
TS migration is still going on |
the typescript migration is still going |
TS migration is still going on |
TS migration is still going on |
changing this issue to weekly as the TS migration finishes in the App repo! 🚀 |
Hey! I’m Błażej Kustra from Software Mansion, an expert agency, and I’d like to work on this issue! I think I can do it as part of this issue, wdyt @hayata-suenaga? |
@blazejkustra, I actually opened a PR for this. However, the reason that we had this babel plugin for Flow was not that we used Flow before, but to do a workaround for a bug with React Native library. However, because this bug is quite old now, I'll try removing the plugin and see if that works. |
seems like we cannot remove this babel config. Closing this issue |
Remove
@babel/preset-flow
frombabel.config.js
once the TS migration is done.from this line
and from this line
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: