Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Breakdown report based on sourcemap

See original GitHub issue

There seem to be a few related issues (#146, #109), but still unsure about the actual answer.

We have two projects:

One uses coffeescript and browserify
The other typescript and grunt-ts

In both project source files (*.coffee \ *.ts) are converted into a single .js file and a source map is created.

Is it possible for the generated report to show a breakdown of the source files, rather than the single concated file?

Issue Analytics

State:
Created 8 years ago
Reactions:3
Comments:6

Top GitHub Comments

1reaction

joeridegcommented, Jan 18, 2016

Any news on this? I think it would be a major breakthrough honestly. It wouldnt matter any more what kinds of compiling / transforming a user does with their source code as long as they output a sourcemap. A user wouldnt have to basicly recreate their build process with all different karma plugins, they could simply include the output file they just created with their build process in the karma files array and still get coverage.

0reactions

Hoofoo-WHUcommented, Feb 26, 2019

It work use karma-coverage-istanbul-reporter replace karma-coverage in TypeScript project