-
Notifications
You must be signed in to change notification settings - Fork 772
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
FlexLayoutModule.forRoot() causing error in 2.0.0-beta.5 #175
Comments
@HarkSolDev - I would imagine you are using angular CLI ? Did you upgrade to @angular/cli Beta.30 or higher? That has upgrade issues with existing CLI projects; nothing to do with flex-layout. Fresh projects (using @angular/CLI beta.30) work great with Flex-Layout Beta.5. Also this plunkr works without issues: http://plnkr.co/edit/QrDjtafk138RVrpS3KBD?p=preview Closing as "not a flex-layout" issue. General discussion and how-to questions should be posted to the community forum areas:
|
Apologies.. your quite right.. Here's the link to a discussion in the angular CLI camp... Thanks for the heads up ! |
@HarkSolDev - great link. Thx.
|
I got the same error with an older project version. Removing |
Do you have the
The Beta.5 version contains the static forRoot() method; with an |
… ngc+aot * 'forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() Refs http://github.com/angular/angular#14410 Fixes #174, Fixes #175, Fixes #176, Fixes #178.
… ngc+aot * 'forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() Refs http://github.com/angular/angular#14410 Fixes #174, Fixes #175, Fixes #176, Fixes #178.
* ‘forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() * updates dependency to minimum of Angular v2.3.1. Refs http://github.com/angular/angular#14410 Fixes #174, Fixes #175, Fixes #176, Fixes #178.
* ‘forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() * updates dependency to minimum of Angular v2.3.1. Refs http://github.com/angular/angular#14410 Fixes #174, Fixes #175, Fixes #176, Fixes #178.
…179) * ‘forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() * updates dependency to minimum of Angular v2.3.1. Refs http://github.com/angular/angular#14410 Fixes #174, Fixes #175, Fixes #176, Fixes #178.
…ngular#179) * ‘forRoot()' fn is never evaluated in AoT, ngc only analyzes the content of the fn to get the module and ngc does not know what to do with the first statetement (console.warn) * clarify changes to FlexLayoutModule.forRoot() * updates dependency to minimum of Angular v2.3.1. Refs http://github.com/angular/angular#14410 Fixes angular#174, Fixes angular#175, Fixes angular#176, Fixes angular#178.
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. |
Just updated to the latest beta ( 2.0.0-beta.5 ) and my project is become very unhappy with the FlexLayoutModule.forRoot() in my angular modules definitions... . did I miss something?
Output:
The text was updated successfully, but these errors were encountered: