angular-cli: build optimizer problem with enum

Bug Report or Feature Request (mark with an `x`)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Versions.

Repro steps.

Sorry I can’t really reproduce the problem. The same code built several times doesn’t even result in the same crash. What is consisent is:

it only crashes when build-optimizer is enabled during build
it never has problems during ng serve
it always crashes at a reference to an enum:

export enum ICommand { show, hide } command.next(ICommand.show);

error is “cannot read properly show of undefined” I have seen several different lines from several components. But always when a enum value is referenced, similar to the line above.

The log given by the failure.

normally it is as above, but once I even got:

bootstrap 6c304fd47c63140fc3b0:54 Uncaught TypeError: Cannot read property ‘call’ of undefined at webpack_require (bootstrap 6c304fd47c63140fc3b0:54) at Object…/…/…/…/…/src/main.ts (index.ngfactory.ts:2882) at webpack_require (bootstrap 6c304fd47c63140fc3b0:54) at Object.0 (index.ngfactory.ts:3190) at webpack_require (bootstrap 6c304fd47c63140fc3b0:54) at webpackJsonpCallback (bootstrap 6c304fd47c63140fc3b0:25) at main.bundle.js:1

and again, it goes away when the optimiser paramter is removed.

Desired functionality.

the ordinal value should be returned

Mention any other details that might be useful.

I hope I can create a small repo that demonstrates the effect, and I wonder if other people has run into it.

I have turned on build-optimizer since it was introduced. My code hasn’t changed much. The lines related to the enum definitely haven’t changed for a long time. I have the impression that the crashes start to appear with CLI 1.4.0. I am still experimenting with different version.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 9
Comments: 19 (6 by maintainers)

Commits related to this issue

fix(TransformationType): move TransformationType to separate file, remove duplicate definition and use strings for the enum type. Fixes #147 See also: https://github.com/angular/angular-cli/issues/761... — committed to realmar/class-transformer by realmar 6 years ago

Most upvoted comments

Sorry about that all. Build optimizer was stripping the export statement out of enums by mistake.

Fixed by https://github.com/angular/devkit/pull/147, verified by https://github.com/angular/devkit/pull/158.

It will be on the next release of the build optimizer and automatically picked up by the CLI.

filipesilva on Sep 20, 2017

Actually I had this as well and forgot to report it 😃 This temporary workaround works for anyone looking for one:

export enum Numbers {
  one: 'one',
  two: 'two',
};

intellix on Sep 12, 2017

@angular/cli @1.4.3 picked up @angular-devkit/build-optimizer @0.0.21. It seems resolved on one of my project but continue to crash the other one.

PS I probably made some mistake earlier. Both my projects are running 0.0.21 without enum problems.

alexfung888 on Sep 25, 2017

I’ve upgraded to “@angular/cli”: “1.5.0-beta.0” and this problem still exists in some cases for me. Sorry for the earlier post.

jponeill on Sep 15, 2017

Had to downgrade my angular/cli version from 1.4.* to 1.3.2 then all warnings disappeared. I can then build with --aot --build-optimizer

iUwej on Sep 14, 2017