Ionic-app-scripts: Slow build

[brandyscarney]

_From @radzik07 on January 14, 2017 15:32_

Ionic v2.2.1
32seconds to build the hello world sidemenu app.
After installing ionic app scripts, 16 seconds:
[16:27:46] build started ...
[16:27:46] transpile update started ...
[16:27:46] transpile update finished in 324 ms
[16:27:46] webpack update started ...
[16:28:02] webpack update finished in 15.71 s
[16:28:02] build finished in 16.06 s

I mean... really? This is that awesome Ionic Framework 2?
Or does it need some extra configuration that wasn't mentioned in tuts?
If not, how the hell can you guys work like this?

_Copied from original issue: driftyco/ionic#10029_

[brandyscarney]

_From @basvdijk on January 14, 2017 16:51_

To give you some reference, these are my build times when I start my app which contains quite some code:

[17:48:50]  ionic-app-scripts 1.0.0
[17:48:50]  watch started ...
[17:48:50]  build dev started ...
[17:48:50]  clean started ...
[17:48:50]  clean finished in 7 ms
[17:48:50]  copy started ...
[17:48:50]  transpile started ...
[17:48:56]  transpile finished in 5.92 s
[17:48:56]  webpack started ...
[17:48:56]  copy finished in 6.22 s
[17:49:10]  webpack finished in 14.04 s
[17:49:10]  sass started ...
[17:49:13]  sass finished in 3.41 s
[17:49:13]  build dev finished in 23.42 s
[17:49:14]  watch ready in 23.54 s
[17:49:14]  dev server running: http://localhost:8100/

After I make a change in a .ts file and saved it:

[17:49:34]  build started ...
[17:49:34]  transpile update started ...
[17:49:34]  transpile update finished in 104 ms
[17:49:34]  webpack update started ...
[17:49:39]  webpack update finished in 5.17 s
[17:49:40]  build finished in 6.63 s

My ionic info

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.5
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: 5.0.13
OS: OS X El Capitan
Node Version: v7.2.0
Xcode version: Xcode 8.2.1 Build version 8C1002

[brandyscarney]

_From @radzik07 on January 14, 2017 19:8_

My ionic info is:
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.5
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: 1.9.0
ios-sim version: Not installed
OS: macOS Sierra
Node Version: v5.12.0
Xcode version: Xcode 8.2.1 Build version 8C1002

Macbook Pro i5 2.53GHz 10GB RAM
@basvdijk is your config stronger?

Just updated node to version 7.2.0.
Sometimes its 8 seconds, most of times its around 16 (when changing .ts file).

Anyone anything?

[brandyscarney]

_From @basvdijk on January 14, 2017 19:10_

@radzik07 Mac Pro 2010, 2x 2.4Ghz Quad Core Xeon, 16GB Ram

But I guess with the transpiling 16 seconds could be considered "normal"

[brandyscarney]

_From @wbhob on January 16, 2017 5:28_

Yeah, that isn't slow. That's normal for everyone. The awesome thing about Ionic 2 is that it is faster and compiled ahead of time, but unfortunately, we developers have to build JiT, so that's unfortunate. But 16s is really fine. Go read an blog post if you need something to do while it builds.

[brandyscarney]

_From @radzik07 on January 16, 2017 18:44_

Okay, I'm getting used to it.
Sometimes its faster, sometimes its slower.
But I noticed there's something not right. From time to time I get into situation the only choice is to restart the app (ctrl+c & ionic serve). It hangs on 'webpack started' forever.

[19:29:41] build started ...
[19:29:41] transpile update started ...
[19:29:41] transpile update finished in 22 ms
[19:29:41] webpack update started ...
[19:29:47] webpack update finished in 5.56 s
[19:29:47] build finished in 16.59 s
[19:29:47] build finished in 5.96 s
[19:30:21] build started ...
[19:30:21] transpile started ...
[19:30:26] transpile finished in 4.33 s
[19:30:26] webpack started ...
[19:33:15] build started ...
[19:33:15] transpile started ...
[19:33:21] transpile finished in 5.32 s
[19:33:21] webpack started ...

I don't know if It was interrupted or something. The thing is that after the first hang, after editing the .ts again, it just starts and hangs. Happened a few times in the last hour. Any way to get more specific info about building? Print some errors?

[mhartington]

Back to the original point.

32seconds

No where in your build out put does 32 second come up.
That build took 16.06 s, which is average.

As for the random hangups on the build, open a new issue here on app-scripts repo.

The build times a bit of a change since we have to constantly transpile from TS to JS that can be run in the browser. It sucks, but we're constantly working on improving it and make things faster.

[danbucholtz]

Consider setting your ionic_source_map_type parameter to eval. That will speed up builds by ~50% or so.

https://github.com/driftyco/ionic-app-scripts#tips

Thanks,
Dan

[linvi]

Sorry but I don't think any developer considers 16 seconds to be a "normal" time for compilation.

In 16 seconds a computer is capable of compiling hundreds of thousands of lines of code.
Here in my case I have an app with few thousands lines of code and the compilation already takes 13 seconds.

PS: Have you tried using Webpack DLL Bundles?

[danbucholtz]

@linvi,

How big is your app? Can you give us a minimal reproduction repository?

I agree that is horribly slow. FWIW, I can rebuild a large sample Ionic app in 2-3 seconds every time on my Mac.

Thanks,
Dan

[linvi]

@danbucholtz

My app is relatively small. 3 tabs => 15 components total.
Regardless of my Windows 10 of Mac Pro 2015 (both high end) the project compile always compile around the same timing.

My mac is around 13 secs compilation while the PC is around 16 secs.

I am telling you that because I really like ionic and the work you do, and I don't want it to change into another meteor where the developers have not been doing anything regarding performances and my company stopped using it for this exact reason, resulting in us using ionic.

[basvdijk]

As quoted before my app takes 6 seconds to rebuild after a change. As a reference I've counted the parts:

• 18 components
• 17 services
• 15 interfaces
• 23 pages
• 6425 lines of typescript code

Used:
find . -name '*.ts' | xargs wc -l inside my app code to count the lines

[rudolfnoe]

I'am facing the same issue:
Starting ionic serve takes 45 sec. That's ok for the first time.

But after changing an .ts file it takes between 12-30 sec to update
[15:36:57] build started ...
[15:36:57] transpile update started ...
[15:36:57] transpile update finished in 451 ms
[15:36:57] webpack update started ...
[15:37:00] webpack update finished in 2.78 s
[15:37:19] build finished in 21.61 s

But what is really interessing that the webpack update only takes 3-8 sec. but the rest more than 15 sec.
I've alread disabled linting as I saw this starts a seperate process.
I've tried to understand what happens after the webpack update has finished but has no clue why it takes so long.

My Ionic info:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.3
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.10.0
Xcode version: Not installed

[wbhob]

Try ionic cli V3. Much faster

On Feb 22, 2017, 9:53 AM -0500, rudolfnoe [e-mail], wrote:
>

I'am facing the same issue:
Starting ionic serve takes 45 sec. That's ok for the first time.

But after changing an .ts file it takes between 12-30 sec to update
[15:36:57] build started ...
[15:36:57] transpile update started ...
[15:36:57] transpile update finished in 451 ms
[15:36:57] webpack update started ...
[15:37:00] webpack update finished in 2.78 s
[15:37:19] build finished in 21.61 s

But what is really interessing that the webpack update only takes 3-8 sec. but the rest more than 15 sec.
I've alread disabled linting as I saw this starts a seperate process.
I've tried to understand what happens after the webpack update has finished but has no clue why it takes so long.

My Ionic info:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.3
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.10.0
Xcode version: Not installed

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/driftyco/ionic-app-scripts/issues/657#issuecomment-281691325), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEpDTq-IIjIEDZIxdm580f9x9Oapaks5rfEv-gaJpZM4Ll9Lj).

[danbucholtz]

@rudolfnoe,

Do you have a very old or very slow computer? These times don't jive with what I've seen at all. My Windows 10 VM that has a minuscule amount of CPU and memory is faster than that.

Thanks,
Dan

[rudolfnoe]

Hi, thank you for your instant replies!

@danbucholtz
No. I have a quite new Lenovo 540p with i7-4700MQ, 16 GB RAM and SSD, but it is a laptop from my company with a lot of stuff on it (even I could deactivate the virsus scanner for node and my dev-folders). I think that will be one reason.

In the meanwhile I could track down what the reason for the slow update build is: It's the full transpile started in build.js --> buildUpdateParallelTasks.
I changed one line of code in build.js-->buildTasksDone:

            //parallelTasksPromise.then(function () {
            Promise.resolve().then(function () {

Now my update is offen done within 3sec. Now it's fun!!! :-)

I think the full transpile has only be started if the transpile update fails. If the transpile update doesn't report an error (which could be stored in the context(?), then the full transpile could be skipped or am I wrong (probably :-)?

Thank you guys for your work and this great framework!!!
Rudolf

[danbucholtz]

We transpile the one changed file AND build the program with type checking (on a separate thread) on every change to validate the correctness of the program. This is by design and I don't think we'll change that.

Thanks,
Dan

[rudolfnoe]

@danbucholtz
Ok, accepted. But maybe a command-line switch would be feaseable, which says "update browser before full transpile has finished". I think the full transpile always take the longest.

[basvdijk]

New build times in 2.4.8 for production

> ionic-app-scripts build "--prod"

[12:49:08]  ionic-app-scripts 1.1.4
[12:49:08]  build prod started ...
[12:49:08]  clean started ...
[12:49:08]  clean finished in 6 ms
[12:49:08]  copy started ...
[12:49:08]  ngc started ...
[12:49:41]  ngc finished in 33.30 s
[12:49:41]  preprocess started ...
[12:49:41]  optimization started ...
[12:49:42]  copy finished in 33.83 s
[12:50:05]  optimization finished in 23.80 s
[12:50:05]  preprocess finished in 23.80 s
[12:50:05]  webpack started ...
[12:51:23]  webpack finished in 78.27 s
[12:51:23]  sass started ...
[12:51:23]  transpile bundle started ...
[12:52:02]  transpile bundle finished in 39.28 s
[12:52:02]  uglifyjs started ...
[12:52:05]  sass finished in 41.61 s
[12:52:05]  cleancss started ...
[12:52:09]  cleancss finished in 3.80 s
[12:53:13]  uglifyjs finished in 70.37 s
[12:53:13]  postprocess started ...
[12:53:13]  postprocess finished in 13 ms
[12:53:13]  lint started ...
[12:53:13]  build prod finished in 245.09 s
[12:53:19]  lint finished in 6.59 s

Build times for ionic serve -b:

[12:56:59]  ionic-app-scripts 1.1.4
[12:56:59]  watch started ...
[12:56:59]  build dev started ...
[12:56:59]  clean started ...
[12:56:59]  clean finished in 1 ms
[12:56:59]  copy started ...
[12:56:59]  transpile started ...
[12:57:06]  transpile finished in 7.03 s
[12:57:06]  preprocess started ...
[12:57:06]  preprocess finished in less than 1 ms
[12:57:06]  webpack started ...
[12:57:06]  copy finished in 7.51 s
[12:57:26]  webpack finished in 20.17 s
[12:57:26]  sass started ...
[12:57:30]  sass finished in 3.83 s
[12:57:30]  postprocess started ...
[12:57:30]  postprocess finished in 1 ms
[12:57:30]  lint started ...
[12:57:30]  build dev finished in 31.09 s
[12:57:30]  watch ready in 31.18 s
[12:57:30]  dev server running: http://localhost:8100/

[12:57:36]  lint finished in 6.41 s

[danbucholtz]

@basvdijk,

Our thought process is we're okay with a slow prod build as long as it produces a lean, mean binary. You shouldn't have to do prod builds often.

Thanks,
Dan

[basvdijk]

@danbucholtz I completely agree! But how do you test your app with native functions e.g. the camera, barcode scanner etc on an actual device? ionic run android without --prod isn't that much faster. And after every change I have to run it again to see if the change worked.

[wbhob]

That's what you have to do. You can also do ionic run --device

Wilson Hobbs
CEO/Founder/Developer at Canal
11th Grade at The Lovett School

Personal Information
E-mail: [email protected]
Cell: [phone]
Website: www.wilsonhobbs.com (https://www.wilsonhobbs.com)
Twitter/Instagram/Facebook: @wbhob

Canal Information
E-mail: [email protected]
Web: www.getcanal.com (https://www.getcanal.com/)

Twitter/Instagram/Facebook: @getcanal

On Mar 21, 2017, 2:08 AM -0400, Bas van Dijk [e-mail], wrote:
>

@danbucholtz (https://github.com/danbucholtz) I completely agree! But how do you test your app with native functions e.g. the camera, barcode scanner etc on an actual device? ionic run android without --prod isn't that much faster. And after every change I have to run it again to see if the change worked.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/driftyco/ionic-app-scripts/issues/657#issuecomment-287986002), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEPIEjJxrZH3gRmT6cGyW0sr8eVs8s45ks5rn2lkgaJpZM4Ll9Lj).

[basvdijk]

@wbhob thanks saved quite some time:

> ionic-app-scripts build "--device"

[12:01:11]  ionic-app-scripts 1.1.4
[12:01:11]  build dev started ...
[12:01:11]  clean started ...
[12:01:11]  clean finished in 5 ms
[12:01:11]  copy started ...
[12:01:11]  transpile started ...
[12:01:18]  transpile finished in 6.56 s
[12:01:18]  preprocess started ...
[12:01:18]  preprocess finished in less than 1 ms
[12:01:18]  webpack started ...
[12:01:18]  copy finished in 7.17 s
[12:01:37]  webpack finished in 19.28 s
[12:01:37]  sass started ...
[12:01:41]  sass finished in 3.70 s
[12:01:41]  postprocess started ...
[12:01:41]  postprocess finished in 1 ms
[12:01:41]  lint started ...
[12:01:41]  build dev finished in 29.59 s

[danbucholtz]

@basvdijk,

You can run ionic run with live reload. Otherwise, you'll do the app-scripts build (dev is much faster than prod) but the real kicker with the full device build is building the native binary, which is the bulk of the time.

See the docs here for live reload with ionic run.

http://ionicframework.com/docs/v2/cli/run/

Thanks,
Dan

[basvdijk]

For reference, building the APK doesn't really take that much time 14 seconds. While building the dev takes over 30 seconds.

$ ionic run android --device

> ionic-app-scripts build "--device"

[07:59:09]  ionic-app-scripts 1.1.4
[07:59:09]  build dev started ...
[07:59:09]  clean started ...
[07:59:09]  clean finished in 4 ms
[07:59:09]  copy started ...
[07:59:09]  transpile started ...
[07:59:16]  transpile finished in 7.37 s
[07:59:16]  preprocess started ...
[07:59:16]  preprocess finished in less than 1 ms
[07:59:16]  webpack started ...
[07:59:17]  copy finished in 7.84 s
[07:59:38]  webpack finished in 21.29 s
[07:59:38]  sass started ...
[07:59:42]  sass finished in 4.51 s
[07:59:42]  postprocess started ...
[07:59:42]  postprocess finished in 1 ms
[07:59:42]  lint started ...
[07:59:42]  build dev finished in 33.22 s
[07:59:49]  tslint
[07:59:49]  lint finished in 6.82 s

BUILD SUCCESSFUL
Total time: 14.612 secs

[basvdijk]

@danbucholtz A few posts back you said:

Our thought process is we're okay with a slow prod build as long as it produces a lean, mean binary.

Is there a command for the apposite? So an "as fast as possible build" without minification etc?

[danbucholtz]

ionic serve or ionic run -l. These builds will be much faster. You can also set the ionic_source_map_type to eval and it'll be faster yet. I am consistently at ~1 second builds with eval, ~2.5-3 second builds with the default source map type.

Thanks,
Dan

[sean-hill]

@danbucholtz I'm currently using @ionic/app-scripts v1.3.7 and I'm facing a build time of over a minute. It seems the webpack update is taking the most time:

[21:57:35]  watch started ...
[21:57:35]  build dev started ...
[21:57:35]  clean started ...
[21:57:35]  clean finished in 3 ms
[21:57:35]  copy started ...
[21:57:35]  transpile started ...
[21:57:40]  transpile finished in 4.79 s
[21:57:40]  preprocess started ...
[21:57:40]  deeplinks started ...
[21:57:40]  deeplinks finished in 176 ms
[21:57:40]  preprocess finished in 177 ms
[21:57:40]  webpack started ...
[21:57:40]  copy finished in 5.25 s
[21:58:30]  webpack finished in 49.66 s - HOLY SMOKES
[21:58:30]  sass started ...
[21:58:31]  sass finished in 1.17 s
[21:58:31]  postprocess started ...
[21:58:31]  postprocess finished in 13 ms
[21:58:31]  lint started ...
[21:58:31]  build dev finished in 55.87 s
[21:58:31]  watch ready in 55.97 s
[21:58:31]  dev server running: http://localhost:8100/

On every hot reload it's also taking about this much time as well 😢 After saving a file in my project:

[21:58:35]  lint finished in 4.22 s
[22:00:28]  build started ...
[22:00:28]  transpile update started ...
[22:00:28]  transpile update finished in 541 ms
[22:00:28]  deeplinks update started ...
[22:00:29]  deeplinks update finished in 855 ms
[22:00:29]  webpack update started ...
[22:01:30]  webpack update finished in 61.22 s - FOR REALS?
[22:01:30]  build finished in 62.66 s

[leetheguy]

I just wanted to put in my 2 cents here.
16s doesn't sound too bad.

That is until you consider that so much of development involves a few small changes then check to see if they worked. Then another change. Then check. And so on.
I frequently will spend no more than 1-2 minutes on changes before seeing if they worked.
When that happens, I'm spending about an 8th of my time waiting.
That means that in an 8 hour day where I'm trying new things rather than fluid coding I can spend a full hour of my time waiting for webpack to build.

I definitely feel the pain for people who take 30-60 seconds or more.

Looking through this thread, I see a couple workarounds I'll have to try.
However, Ionic makes everything so much smoother and easier, it would be really nice if the build process was smoother as well.

[danbucholtz]

How do I recreate the slow build issues? Are you utilizing code splitting?

Thanks,
Dan

[leetheguy]

I think it may be difficult or impossible to recreate slow build issues. I have a standard 2015 MacBook Pro with 16GB ram and an SSD drive. A hello world app that I just created takes 16s to compile every time I save a ts page. Near the top of this thread, they said it's normal and closed the topic.

I think a better approach is to help people learn to optimize webpack. The comment you made about ionic_source_map_type worked like a charm. And it did cut my build time in half as you said. So thank you for that!

That information was not easy to find though, and I have no idea what it's actually doing. As for code splitting, a brief glance makes it seem really complex unless you have a deep understanding of Webpack. As an Ionic dev though that's rarely necessary because Ionic shelters you from that. That and I don't like to edit anything inside the node_modules folder because it could be wiped in an update. It would be nice if I could just go ionic serve --optimaldev or something like that and Ionic would implement ionic_source_map_type, code splitting, and whatever else the gurus know would speed things up.

[ntbnnt]

For what it is worth, our team has been using the ionic serve command and we were getting very slow build times. I added a webpack config that seemed to speed things up by splitting out some large dependencies. This appeared to help but optimized defaults would be greatly welcomed.

[danbucholtz]

I intend to look into slow build times in the next week.

Thanks,
Dan

[rickyk586]

@danbucholtz There is also an issue I'm experiencing when saving multiple files at the same time, not all of the changes are reflected in the browser even after a refresh. Probably not related but since you'll be in the code... (man I hate when people say that)

[basvdijk]

Here the build times of my app, it has quite some components, pages and libraries (using app script 1.3.12)

[16:15:19]  build started ...
[16:15:19]  transpile update started ...
[16:15:19]  transpile update finished in 131 ms
[16:15:19]  deeplinks update started ...
[16:15:19]  deeplinks update finished in 208 ms
[16:15:19]  webpack update started ...
[16:15:32]  webpack update finished in 13.23 s
[16:15:32]  build finished in 13.59 s

[16:15:59]  build started ...
[16:15:59]  transpile update started ...
[16:15:59]  transpile update finished in 103 ms
[16:15:59]  deeplinks update started ...
[16:16:00]  deeplinks update finished in 429 ms
[16:16:00]  webpack update started ...
[16:16:10]  webpack update finished in 10.31 s
[16:16:10]  build finished in 10.85 s

[16:18:05]  build started ...
[16:18:05]  transpile update started ...
[16:18:06]  transpile update finished in 320 ms
[16:18:06]  deeplinks update started ...
[16:18:06]  deeplinks update finished in 361 ms
[16:18:06]  webpack update started ...
[16:18:21]  webpack update finished in 15.05 s
[16:18:21]  build finished in 15.76 s

[17:38:04]  build started ...
[17:38:04]  transpile update started ...
[17:38:04]  transpile update finished in 97 ms
[17:38:04]  deeplinks update started ...
[17:38:04]  deeplinks update finished in 451 ms
[17:38:04]  webpack update started ...
[17:38:14]  webpack update finished in 9.34 s
[17:38:14]  build finished in 9.90 s

[11:35:41]  build started ...
[11:35:41]  transpile update started ...
[11:35:42]  transpile update finished in 913 ms
[11:35:42]  deeplinks update started ...
[11:35:43]  deeplinks update finished in 1.06 s
[11:35:43]  webpack update started ...
[11:35:52]  webpack update finished in 8.43 s
[11:35:52]  build finished in 10.46 s

[danbucholtz]

@basvdijk,

Yeah, that is really slow. What are your computer specs? It takes me between 3-4 seconds on a slow refresh, 2-3 on a fast. I have a really fast Mac, though.

Thanks,
Dan

[basvdijk]

@danbucholtz I have a Mac Pro (mid 2010), 2x 2.4Ghz Quad core, 16GB ram and PCI-E SSD, OSX 10.11.

The app consists of:

• 22 pages (4419 lines of TS code)
• 23 components (1845 lines of TS code)
• 24 services (2614 lines of TS code)

[wbhob]

Oml that's very very heavy @basvdijk can you not consolidate any of your services or components? I can understand having dozens of pages, but the other stuff you should be able to consolidate to some degree

[basvdijk]

@wbhob If I may ask, why do you see a solution in consolidating components? Isn't the idea to split the code into modules/parts instead of making big ones?

[wbhob]

You're right, but hyper-modularizing can be problematic. If you're only using a component once, then it might be best to bake it into the page.

Also, I don't know about your config, but if you have a ComponentsModule and you're using lazy loading, that could be your culprit @basvdijk

[danbucholtz]

In theory lazy loading should make the build faster. I am taking a look at this as we speak.

Thanks,
Dan

[basvdijk]

Interesting! I am currently refactoring my app so lazy loading could be applied once Ionic supports this :)

[jonathanwoahn]

@danbucholtz Any updates on your dive into the slow build times? We're consistently seeing initial ~30s for slow and 15-20s for fast. I have a "really fast mac", but it doesn't seem to make a difference.

[danbucholtz]

Sorry, we are as optimized as we can be right now. You can try disabling the build_to_es5 flag. Please double check the readme to make sure the flag is correct.

Thanks,
Dan

[rudolfnoe]

Only to reiterate: Tweaking the node_modules/@ionic/app-scripts/dist/build.js cuts down the dev cyle significantly. Just replace one line of code in the buildUpdate Method

    function buildTasksDone(resolveValue) {
        // all build tasks have been resolved or one of them
        // bailed early, stopping all others to not run
       //===========================================//
        //parallelTasksPromise.then(function () {  --> Commented out for speedup dev cycle
        Promise.resolve().then(function () {  //--> Added instead
       //===========================================//

Build times without the tweak:
[09:17:38] build started ...
[09:17:38] transpile update started ...
[09:17:38] transpile update finished in 47 ms
[09:17:38] deeplinks update started ...
[09:17:39] deeplinks update finished in 219 ms
[09:17:47] build finished in 9.24 s

[09:18:01] build started ...
[09:18:01] transpile started ...
[09:18:11] transpile finished in 9.47 s
[09:18:11] deeplinks update started ...
[09:18:11] deeplinks update finished in 219 ms
[09:18:11] webpack update started ...
[09:18:16] webpack update finished in 5.25 s
[09:18:16] sass update started ...
[09:18:19] sass update finished in 3.11 s
[09:18:19] build finished in 18.10 s

[09:18:19] build started ...
[09:18:19] transpile started ...
[09:18:29] transpile finished in 9.59 s
[09:18:29] deeplinks update started ...
[09:18:29] deeplinks update finished in 173 ms
[09:18:29] build finished in 9.77 s

Build times with the teak:
[09:12:57] build started ...
[09:12:57] transpile update started ...
[09:12:57] transpile update finished in 42 ms
[09:12:57] deeplinks update started ...
[09:12:58] deeplinks update finished in 277 ms
[09:12:58] webpack update started ...
[09:13:03] webpack update finished in 5.10 s
[09:13:03] build finished in 5.51 s

[09:13:08] build started ...
[09:13:08] transpile update started ...
[09:13:08] transpile update finished in 30 ms
[09:13:08] deeplinks update started ...
[09:13:08] deeplinks update finished in 321 ms
[09:13:08] webpack update started ...
[09:13:09] webpack update finished in 1.19 s
[09:13:09] build finished in 1.62 s

[09:13:13] build started ...
[09:13:13] transpile update started ...
[09:13:13] transpile update finished in less than 1 ms
[09:13:13] deeplinks update started ...
[09:13:13] deeplinks update finished in 98 ms
[09:13:13] webpack update started ...
[09:13:16] webpack update finished in 3.06 s
[09:13:16] build finished in 3.17 s

Drawback:
Compile errors in files shows up only after the fully rebuild has finished.

I would really appreciate if there would be a config option to tweak this!!!