Profiling about karma-webpack HOT 10 CLOSED

In case of tests this 892 modules of which 295 are transpiled with babel.

from karma-webpack.

Do you use the alternative useage?

from karma-webpack.

Yes. I think the test bundle takes 30-40 seconds to compile if I use babel. And 10 seconds without babel which is acceptable. Maybe this project is just too large, or maybe I shouldn't be always running all tests - but the latter is not easy with karma.

from karma-webpack.

I'm thinking about building another karma-webpack like plugin which allows a --grep arg to filter which test files get bundled. Is that of interest to anyone? :-"

from karma-webpack.

I think I managed to add some simple grepping via ContextReplacementPlugin

// my test-main.js
var testsContext = require.context("../..", true, /_test$/);
testsContext.keys().forEach(testsContext);

// karma.config.js
...
if (argv.grep) {
    webpackConfig.plugins = _.union(webpackConfig.plugins, [
      new webpack.ContextReplacementPlugin(new RegExp('../..'), function (result) {
        result.regExp = new RegExp('.*' + argv.grep + '.*_test$');
      })
    ]);
  }
...

This allows me to run karma start --grep foo to filter some subset of tests to build with webpack, leaving full test runs to CI.

from karma-webpack.

I just gave this a try and my test time increased by 2 seconds... Very odd.

from karma-webpack.

Perhaps that's the case for small sets of tests. For me, when I grep a small subset of tests, the time decreases from 2minutes to 15 seconds.

from karma-webpack.

I've just blogged about the --grep trick https://medium.com/@kidkarolis/karma-webpack-grep-super-fast-tests-in-dev-b11130e2c2c6 in case anyone's interested.

from karma-webpack.

Hi @KidkArolis nice post. I had a similar issue as yours due to our very large code base. Your post may solve our test problem. But I wonder how do you solve your incremental build issue (you should also have). I run webpack in watch mode, but whenever I change a file, it takes over 1 minute to compile&bundle which is way too long for developer.

from karma-webpack.

In my experience the incremental build is only slow if you use the wrong
sourcemap (devtool) option. Try them all to find the fast one..
On Fri, 12 Feb 2016 at 17:55, Larry He [email protected] wrote:

Hi @KidkArolis https://github.com/KidkArolis nice post. I had a similar
issue as yours due to our very large code base. Your post may solve our
test problem. But I wonder how do you solve your incremental build issue
(you should also have). I run webpack in watch mode, but whenever I change
a file, it takes over 1 minute to compile&bundle which is way too long for
developer.

—
Reply to this email directly or view it on GitHub
#47 (comment)
.

from karma-webpack.