Am I still supposed to use the karma-coverage fork? #38
Comments
I don't know... I will be testing this tonight |
+1 Also getting exact error/stacktrace using karma-coverage@0.3.1 |
+1 I can report the same, works fine with fork, does not work against karma-coverage@0.3.1 |
Everything is working fine for me without using the fork. I'm using |
Not seeing this error now using karma-coverage@0.4.2 |
No need for the fork anymore :) If there is the need change something to make it work, please open a PR/issue on karma/karma-coverage |
If this is the case, could you update the README to indicate this @douglasduteil? Thanks! |
I can confirm I didn't need the douglasduteil/karma-coverage#next fork. |
I just tried to switch to |
Having the same problem with 0.5.3. I see ES5 code instead of ES6. |
Is this a problem with isparta or karma-coverage? +1 to fixing this either way. |
+1 |
I'm trying karma coverage 0.3.1. karma-runner/karma-coverage/pull/130 was merged, but I'm getting the following error:
It works with the fork though.
The text was updated successfully, but these errors were encountered: