-
Notifications
You must be signed in to change notification settings - Fork 46
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
Babel 7 #30
Comments
If the babel team publish a guide for plugin authors to migrate, we can add support for babel 7. Failing that, once babel 7 is fully released, we could upgrade this library to babel 7 as a breaking change. At the moment, we still need to support babel 6. |
I've not met any issue with babel 7 on my projects. In case you have something which blocks you, share with us please. |
I'm getting this message:
It looks to me like this is an issue with the new naming conventions of Babel 7, as stated above. Probably changing |
We finally start supporting babel v7. As expected, it took more effort than just changing the number in package.json. Among babel I updated other dependencies (apart from lint-staged, because in their changelog I saw they require Node >8.6, which I decided to fix within other PR). Initial request: #30 ### Todo - [x] Use new interface of @babel/cli (now we copy unwanted files) - [x] Make sure tests for built version are passes
@shirohana @stevenxxiu @jasperandrew we now officially support babel@7 starting from 7.0.0 version of this plugin. |
Babel 7 uses
require('@babel/core');
now, substituting that in the source appears to work.A temporary fix now is to install
babel-core^7.0.0-bridge.0
.The text was updated successfully, but these errors were encountered: