-
Notifications
You must be signed in to change notification settings - Fork 773
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
Webpack fails to compile updating from beta.4 to beta.5 using angular-cli #174
Comments
Thanks I had the same issue when I update Angular Cli to 1.0.0-beta.31 and Angular 2.4.7. I confirm reverting flex-layout back to beta.4, resolves the issue. |
@d3viant0ne - I have discovered real challenges with upgrading CLI to beta.30. It seems the CLI team's recommendation is to start "fresh"... (which seems horrible BTW). And I think this mix of old/new CLI has issues with flex-layout.
|
I haven't dared update my current work project to beta.31 yet given the problems I have had in the past. The best way I have found to do it is run run |
Closing as "not a flex-layout" issue |
Here is the issue related to angular-cli beta.30: @daveo1001 - I think this is an issue for angular-cli... not Flex-Layout. |
@ThomasBurleson looks like a flex-layout issue, guy. It worked yesterday when I was using cli beta 30 and flex-layout beta 4. What you linked has nothing to do with what I'm experiencing. |
@daveo1001 - investigating. |
@ThomasBurleson thanks! |
@daveo1001 - I just tried this with a completely new, blank folder... and followed your steps. It works great!
import { FlexLayoutModule } from '@angular/flex-layout';
import { AppComponent } from './app.component';
@NgModule({
declarations: [
AppComponent
],
imports: [
BrowserModule,
FormsModule,
HttpModule,
FlexLayoutModule
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }
All works great. |
Son of a bee sting. I've got the same issue on two different computers. Windows 10 screwing me, maybe? |
Ah... the notorious Windows OS. Yep. Betcha a $10.
|
Busted on Windows 7 too. :/ |
Quick, @ThomasBurleson let me borrow your computer. |
Not sure if this is any help to anyone but I just got rid of the error by removing the
to
|
Windows 10 version: Ultimate Pro Majestic Supreme .. .. angular-cli: 1.0.0-beta.24
When I import FlexLayoutModule = "Unexpected value 'undefined' imported by the module 'AppModule'"When I remove it from the import = happily ever after... Was barely going to check out FlexLayout and this happened.. .. :'( sniff .. . . So.... I ended up setting @angular/flex-layout: 2.0.0-beta.4 to start get intimately acquainted with angular flexLayout |
@ThomasBurleson does this mean you owe me $100? 😁 |
… 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.
@daveo1001 - It means I owe you $10 (see #174 (comment)). send me your email and I will gift you an iTune card. |
@ThomasBurleson emailed! |
Well after a failed attempt of trying to use angular FlexBox last week.. . I decided to give it another shot (in da face.. .) To get it working, I ended up: Upgrading FROM @angular-cli: 1.0.0-beta.24 TO @angular/cli: 1.0.0-beta.31 Cheerio mates 🤓 |
…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. |
During
ng serve
I get: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 AppModule in blah/blah/src/app/app.module.ts, resolving symbol AppModule in blah/blah/src/app/app.module.ts
Compiles fine when I change angular/flex-layout back to beta.4.
angular-cli beta 31
Let me know if any additional info would be helpful.
The text was updated successfully, but these errors were encountered: