-
Notifications
You must be signed in to change notification settings - Fork 47
Babel can't parse _mocha #47
Comments
Looked into this a bit since it was also reported to Babel and it seems like something has changed in |
Looks like mocha has merged mochajs/mocha#1787 so this shouldn't be an issue in the future. @leebyron Looking at this a bit more after playing with it myself, if you have your code in a subfolder, it seems setting the instrumentation root avoids this too. .istanbul.yml
|
Thanks for the investigation! This has been very helpful — On Mon, Jul 13, 2015 at 11:23 AM, Logan Smyth notifications@github.com
|
Thank you @loganfsmyth . Your |
Still getting transpile errors with mocha@2.3 and the istanbul config file does little to resolve this.
weird thing is that it is working when npm is in charge of running the command (another Component) but that same command fails from the CLI and altered slightly to work without npm. |
Hi @leebyron After some code surfing 🏄 Here is deduction http://tonicdev.com/douglasduteil/isparta-68-transformation-error-return-original-code |
Is this still a problem? I was unable to reproduce it. |
Yes, just ran into this. Following @douglasduteil's suggestion, I changed my invocation from:
to:
and no longer get this error. |
Hi everyone) I using isparta as @chromakode said few days ago: |
The workaround of |
Node already support es6, just call like this: Thats all you need) |
@glebmachine Not sure I follow, my current command is: |
Sorry for misunderstanding! Everything i ok. I'm using like u said, and everything fine: Please, ignore my prev comment) |
It is now working with |
When running
As suggested by the README, I encounter this error:
The text was updated successfully, but these errors were encountered: