-
Notifications
You must be signed in to change notification settings - Fork 12k
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 after optimize not a function error #12146
Comments
From @filipesilva on February 22, 2018 21:20 This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please? You can read here why this is needed. A good way to make a minimal repro is to create a new app via |
From @vincentjames501 on April 27, 2018 20:5 Try importing from here instead ( |
Might be this issue ReactiveX/rxjs#4070 |
Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information. If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
From @Mightforanis1938 on February 16, 2018 14:20
Bug Report or Feature Request (mark with an
x
)Area
Versions
node --version v8.9.4
npm --version 5.6.0
Repro steps
I have an angular module with an observable timer
module Inports:
and after build with build optimizer:
The log given by the failure
message: "o.a.timer is not a function"
stack: "TypeError: o.a.timer is not a function"
It works when the set to --build-optimizer=false but when is turned on and after the build when the scheduleRefresh is called throws a not a function error
it does not work with "@angular-devkit/build-optimizer": "0.4.0" either.
Copied from original issue: angular/devkit#443
The text was updated successfully, but these errors were encountered: