-
Notifications
You must be signed in to change notification settings - Fork 43
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
ava and "Unexpected token import" #58
Comments
Looks like a cache issue. I tried deleting node_modules/.cache/ava but no luck. Babel cache is supposed to not be used according to BABEL_DISABLE_CACHE. |
looks like for some reason it does not expect that index.js is es6 module. Will try today to add ava to tests. |
Also sometimes I got problems with this presets sequence
and now prefer (it's undependent of plugin, but some of my code does not compile with your presets sequence) |
Good news, I've reproduced this error. |
Thank you, fixed, 0.4.0 in npm (I have no idea why it worked before even on mocha) I'm not sure that current fix is good (or I'm sure it's not a good idea to call babel-register inside plugin) (the better is to require config in some isolated env) but all tests working fine and ava too. |
Yeah. I'm concern about this too. What if I have babel-register inside the code ? |
Tests have |
I have this issue in case:
Why it skips babel settings? :) |
It skips babel settings in webpack loaders. Not all babel setting. |
Hi,
I am trying to run tests with AVA and your plugin.
At the first place, it wasn't working (error below). I rm -rf node_modules, then tried again and it was working (tests on jsx and react were failing as expected). No idea why, I changed a string in my file, and got this error:
I reverted my changes but same problem.
Note that I run with the following command (I just pasted interesting part)
I cannot share my webpack config as it's very messy and private, just be sure that I use this
The text was updated successfully, but these errors were encountered: