FlexLayoutModule.forRoot() causing error in 2.0.0-beta.5

[HarkSolDev]

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:

ERROR in Error encountered resolving symbol values statically. 

Calling function 'FlexLayoutModule', function calls are not supported. 
Consider replacing the function or lambda with a reference to an exported function, 
resolving symbol SidenavModule in D:/[REDACTED]/sidenav/sidenav.module.ts,
resolving symbol SidenavModule in D:/[REDACTED]/src/app/modules/sidenav/sidenav.module.ts

[ThomasBurleson]

@HarkSolDev - FlexLayoutModule.forRoot() was deprecated, but not removed. You should see a console.warn() message in the console. However your error ^ appears to be unrelated.

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:

• Google Groups
• Gitter Channel - note this will be available soon...

[HarkSolDev]

Apologies.. your quite right.. Here's the link to a discussion in the angular CLI camp...
angular/angular-cli#4425

Thanks for the heads up !

[ThomasBurleson]

@HarkSolDev - great link. Thx.

Solutions re the @angular-cli issue: angular/angular-cli#4425 (comment)

[cre8]

I got the same error with an older project version. Removing .forRoot() worked for me.

[ThomasBurleson]

Do you have the forRoot() method in your local flex-layout.umd.js file:

Here is the beta.5 version flex-layout.umd.js

The Beta.5 version contains the static forRoot() method; with an /** @deprecated */ comment.
So I am unclear why you are encountering your error(s).

[ThomasBurleson]

@HarkSolDev, @cre8 - @see #176 (comment)