-
Notifications
You must be signed in to change notification settings - Fork 247
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
Breakdown report based on sourcemap #193
Comments
+1 , using systemjs-builder for example it would be nice to have the report on the source files and not the generated output. I think the general problem is: Supporting sourcemaps would solve this kind of problems in a very generic way instead of trying to create seperate plugins like karma-systemjs or karma-jspm etc to recreate the building and concatenating of all source files. |
Any news on this? |
Any update on this? It would make it so much more flexible for users with different build systems. Re-creating the build in Karma is a hassle and also introduces the possibility of false negatives/positives if the build and the Karma configuration diverge. |
I tried Currently, I cannot run |
I have also tried using |
It work use |
There seem to be a few related issues (#146, #109), but still unsure about the actual answer.
We have two projects:
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?
The text was updated successfully, but these errors were encountered: