-
Notifications
You must be signed in to change notification settings - Fork 249
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
TypeError: cannot read property 'split' of undefined #278
Comments
I am having this same issue too. I'm using fountainjs to generate webapp, using Angular 1 with bower dependencies and injection, configured it to do coverage, ran the test and it passed the test and when generating the report, it failed with this error. However, the output gets generated. |
maybe this answer will help you ,istanbul-instrumenter-loader / html reports fail w/ v1 #32 |
no updates? |
I've been trying to figure out this problem for a couple of days myself. Please let me know if you figure anything out |
Ive been doing some debugging and I suspect the root cause is This is the config for the project Im working on:
Despite the The failure results from coverage report for I am not well versed in the internals of |
I think you're on the right track. I really wish someone could solve this. I haven't had any luck. |
I haven't made much progress. Ive tracked the bug to here the result parameter contains the invalid coverage property. However I cannot find the source of it. The only place I can find If someone knows where this event is being emitted from let me know. |
I believe there's a PR for this here: gotwarlost/istanbul#816 |
- As the code need to be applied _inside_ the webpack, the relevant loader must be used. - Using a fork of the loader because it can generate html reports without dying in a fire like the official one. - karma-runner/karma-coverage#123 - karma-runner/karma-coverage#278
- As the code need to be applied _inside_ the webpack, the relevant loader must be used. - Using a fork of the loader because it can generate html reports without dying in a fire like the official one. - karma-runner/karma-coverage#123 - karma-runner/karma-coverage#278
Looks like Istanbul is not being maintained. I saw a sad comment on one of the PRs related to this issue, according to last comment on this gotwarlost/istanbul#816 (reference) @gotwarlost is not active. |
Thank you @michaelBenin |
Hi,
version: 1.1.1
I am using Karma-coverage to generate lcov report with in-memory report like this:
I am getting the error:
I tried modifying the html.js to see the result. coverage is sending undefined value to istanbul in the end.
My reports are generating properly, but this error fails my build.
Is there a fix to it?
The text was updated successfully, but these errors were encountered: