istanbul-instrumenter-loader
istanbul-instrumenter-loader copied to clipboard
webpack-contrib
Istanbul Instrumenter Loader
First off, I have little understanding of the interactions amongst karma, webpack, istanbul-instrumenter-loader, and karma-coverage. This may not be the appropriate project for my request and, if not, maybe you...
`"istanbul-instrumenter-loader": "^1.2.0",` There exists an index.ts library file with some * exports. ``` //index.ts export * from './some-file' ... ``` When importing this new library file with the loader argument...
After upgrading to babel 7 I started receiving the error, and none of the related issues I have found helped to solve it. Removing the istambul-instrumenter-loader rule from the webpack...
this is my webpack configuration in karma.conf.js: ```javascript webpack: { module: { rules: [ { test: /\.js$/, use: [{ loader: 'babel-loader' }], exclude: /(node_modules)/, }, { test: /\.js$/, use: [{...
The sourcemaps that `istanbul-instrumenter-loader` returns are not using the input sourcemap to provide sourcemaps back to the source. This can be reproduced in the tests for this repo. - modify...
I am using istanbul-instrumenter-loader to generate code coverage for my project. I am getting incorrect branch coverage every since I upgraded my typescript from 2.9.2 to 3.0.3 (latest). The following...
Using latest version of istanbul-instrumenter-loader (v3.0.0) and found the coverage report generated covers node_modules/webpack/buildin/module.js file along with other source code. I think this is unnecessary. Node version: 7.9.0 OS: macOS...
Is there any solution for projects using ES6 syntax? The problem is that it doesn't seem possible doing that require matching all test files and tested files.
