Repository navigation
enum in separate file throws runtime error when built with AOT #10983
Description
Versions
Angular CLI: 6.0.3
Node: 8.11.1
OS: win32 x64
Angular: 6.0.3
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.6.3
@angular-devkit/build-angular 0.6.3
@angular-devkit/build-optimizer 0.6.3
@angular-devkit/core 0.6.3
@angular-devkit/schematics 0.6.3
@angular/cdk 6.1.0
@angular/flex-layout 6.0.0-beta.15
@ngtools/webpack 6.0.3
@schematics/angular 0.6.3
@schematics/update 0.6.3
rxjs 6.2.0
typescript 2.7.2
webpack 4.8.3
Repro steps
On opening the resulting webpage i receive Cannot read property 'none' of undefined errors. Those errors result from undefined enums at runtime.
Very much simplified example (with 2 separate files)
action-type.enum.ts (enum in separate file)
export enum eActionType {
none,
actionA
...
}
test.component.ts (component in separate file)
import { eActionType } from './action-type.enum';
@component({ ... })
export class Test {
// @Runtime eActionType (eActionType.none) will be undefined
private/protected/public actionType: eActionType = eActionType.none;
Observed behavior
runtime error but only when building in AOT
Desired behavior
enum should not be undefined
Activity
Principe92 commentedon May 24, 2018
I am getting the same error. If I run
ng serve aotI don't get the error. However, if I runng build --prod --aotI get the error[-]enum in separate file throws runtime error what built with AOT[/-][+]enum in separate file throws runtime error when built with AOT[/+]Principe92 commentedon May 24, 2018
@dsoltesz according to https://github.com/angular/angular-cli/issues/10655, setting the
"buildOptimizer": false,in angular.json seems to fix it.dsoltesz commentedon May 24, 2018
Doesn’t that kinda negate the benefits of using aot?
Principe92 commentedon May 24, 2018
@dsoltesz Yep. I guess we will have to turn it off until they fix it.
dsoltesz commentedon May 29, 2018
is anyone going to look at this...seems to be a pretty big regression, enums not working in AOT?
dsoltesz commentedon Jun 7, 2018
This is a breaking change from past releases. Is there any target build that this will be addressed? Or any work around for the time being?
Invis1ble commentedon Jun 7, 2018
set
buildOptimizertofalseinangular.jsondsoltesz commentedon Jun 7, 2018
this does work but obviously lose that optimization...hopefully someone will fix this.
filipesilva commentedon Jun 7, 2018
Heya, does this still happen with the latest 6.0.x releases?
filipesilva commentedon Jun 7, 2018
Actually, I'm going to close in favor of #10655. It seems to be the exact same thing but there's some more information and a better repro there.
dsoltesz commentedon Jun 7, 2018
this didn't start happening until we upgraded to 6.0.x
dsoltesz commentedon Jun 7, 2018
ok, will subscribe to that post, thanks
angular-automatic-lock-bot commentedon Sep 8, 2019
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.