How to run angular cli ng test with production build settings and AOT enabled

Question

Is there a way to run the angular cli tests with the command ng test that tells the underlining compiler to use the ng build --prod settings?

I ask because here are often aot compilation errors encountered with ng build --prod that do not occur with normal compilation with ng build

Any clue on that? I think that's a very important point. – Bob May 25 '18 at 16:48 — Bob, May 25 '18 at 16:48

Trevor Karjanis · Answer 1 · 2019-07-18T15:32:36.937

3

This is not possible, and I think that is because the test architect target is its own build configuration. Options like assets, scripts, and styles are supported, but options that are typically associated with production, like AOT, are not. This is because the compiler team considers the feature to be experimental. There is a feature request to support AOT.

To create a production configuration, add it to the test target.

"test": {
  "builder: "@angular-devkit/build-angular:karma",
  "options": {
    ...
  },
  "configurations": {
    "production": {
      ...
    }
  }
}

edited Jul 18 '19 at 15:32

answered Jul 09 '19 at 18:10

Trevor Karjanis

1,485
14
25

Does anyone has any up-to-date info on this experimental feature? Maybe @Trevor Karjanis? Thanks! – ddsultan Feb 16 '23 at 07:17

score -3 · Answer 2 · edited Dec 06 '17 at 13:42

-3

Have you tried ng build --aot ?

https://angular.io/guide/aot-compiler

To test with production settings you could use ng test --environment=prod.

edited Dec 06 '17 at 13:42

Neeraj Kumar

771
2
16
37

answered Dec 06 '17 at 11:35

Eduard Ghinea

87
1
8

1

Thing is that adding --environment=prod will not trigger what --prod flag triggers, especially minification (which is my main source of troubles). I truly wander how real prod builds can actually be tested. – Bob May 25 '18 at 16:48

How to run angular cli ng test with production build settings and AOT enabled

2 Answers2