Routing: canActivate is not created in --prod when using concat

🐞 bug report

Description

When using array_of_guards.concat(guard) as canActivate parameter in a route and building app with --prod the resulting script doesn’t have canActivate variable defined. When using […array_of_guards, guard] it works fine. The issue doesn’t show when not in --prod meaning that a dev environment works fine.

🔬 Minimal Reproduction

https://github.com/mlechnioppg/guards-bug

Clone repo then run: ng build --prod Use http-server to run, eg: http-server dist/guards Click links while watching console and see that guards don’t fire when clicking one link. When testing using ng serve all logs show properly when clicked.

🌍 Your Environment

Angular Version:

Angular CLI: 7.3.6
Node: 8.12.0
OS: win32 x64
Angular: 7.2.9
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.12.4
@angular-devkit/build-angular     0.12.4
@angular-devkit/build-optimizer   0.12.4
@angular-devkit/build-webpack     0.12.4
@angular-devkit/core              7.2.4
@angular-devkit/schematics        7.3.6
@angular/cli                      7.3.6
@ngtools/webpack                  7.2.4
@schematics/angular               7.3.6
@schematics/update                0.13.6
rxjs                              6.3.3
typescript                        3.2.4
webpack                           4.28.4

Anything else relevant?

[Stanteq]

I have the same issue when I want to attach the guard for all routes

const routes: Routes = [{
    path: "",
    loadChildren: "./home/home.module#HomeModule",
    data: { }
  },  {
    path: "test",
    loadChildren: "./test/test.module#TestModule",
    data: { }
  }]

 routes.forEach((route: Route) => {
   route.canActivate = [GuardService];
 });

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}