-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Fails to run with react-native project using babel 7 #627
Comments
I am having the exact same problem since upgrading to 0.56.0. Cannot run a single new project. |
@iljadaderko @tjb295 -- The current The deal is that react-native now ships flow-types in-project (instead of stripping them), and babel7's basic structure explodes if both flow & typescript transformers are loaded at the same time. |
@sebinsua whats the status there? I assume babel needs to be removed, but this can't be done due to tests? |
This is an issue because dangerjs is still using babel-7 alpha and the consuming project is using babel7 stable. |
Danger's deps only include babel-polyfill - do you have a sense about why it would be affecting a babel7 build? |
We're working with babel 7 - so this should be fixed |
I just got following error when I ran danger (this doesn't happen when I run commands like lint, jest or flow, so led me to think this is something danger specific?)
Issue started appearing when I upgraded my react-native project to v0.56.0, with this an update to babel v7 happened as well as I now need to use
latest
version of babel-preset-react-native which I believe is referenced in the error.Besides danger my project and other tooling that remotely relies on babel seem to be working fine.
The text was updated successfully, but these errors were encountered: