Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build optimizer problem with enum (the Second) #10726

Closed
rlexa opened this issue May 8, 2018 · 2 comments
Closed

build optimizer problem with enum (the Second) #10726

rlexa opened this issue May 8, 2018 · 2 comments

Comments

@rlexa
Copy link

rlexa commented May 8, 2018

See issue 7613 which is currently closed but seems to have resurfaced now.

Versions

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

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.6.0
@angular-devkit/build-optimizer   0.6.0
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@angular/cdk                      6.0.1
@angular/material                 6.0.1
@ngtools/webpack                  6.0.0
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Windows 7
"@tensorflow/tfjs": "^0.10.3"

Repro steps

Using tensorflow/tfjs package and training any model with e.g. scalar variables.

Observed behavior

Using (in my case) tensorflow/tfjs package in prod fails with undefined when trying to use the TextureType enum in this file of theirs (figured out by activating the source maps in prod). Circumvented the problem for now by deactivating buildOptimizer in prod.

Desired behavior

Exported enums should be available in prod with activated buildOptimizer.

Mention any other details that might be useful (optional)

Maybe same problem as was in 7613?

@clydin
Copy link
Member

clydin commented May 8, 2018

Duplicate of #10655

@clydin clydin marked this as a duplicate of #10655 May 8, 2018
@clydin clydin closed this as completed May 8, 2018
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants