-
Notifications
You must be signed in to change notification settings - Fork 61
exportDefaultFrom
error from parser after upgrade to 1.4.0
#228
Comments
v1.5.0 has been published. |
Awesome, thanks for the quick fix @chinesedfan! I've now added A question from my side: I think it would be better if the plugin could simply use the same configuration as I use for babel i.e. |
I am on latest version of this package, as well as babel, but I am still receiving this error. Any ideas as to why that might be the case? |
@rtymchyk Have you changed your configurations like this? If still met this problem, feel free to open a new issue with detailed environments information. |
@chinesedfan Sorry, I misread. I thought the PR was including this as a plugin already. Working fine now, but definitely would be great to utilize the central Babel config instead of this. |
For those who stumbled upon this issue from Google and are confused, just add this to your
|
I'm currently in the process of updating from version
1.3.2
to1.4.0
. As I can see from the changelog, babel errors are now shown to users. I'm now getting a few of those:The files where this occurs are very simple e.g.:
How can I configure the parser used by this plugin to allow for the experimental syntax? Am I doing something wrong?
The text was updated successfully, but these errors were encountered: