flex-layout: Angular CLI + @angular/flex-layout unrecognized

Hi ! Happy New Year !!

I use on my project “angular-cli”, “angular material2” and “angular flex layout”. I thought I had imported Correctly “angular flex layout” but I do not think it works on my app. Still, I have applied the implementation tips of the lib.

So I wanted to test the same code on a plunker : Example Test

And as you can see, it works. So I have a problem with the recognition of the bookstore which in my opinion is not recognized by my app.

In app.module.ts :

// angular modules
...
import { FormsModule } from '@angular/forms';
// angular-material2 modules
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { FormsModule } from '@angular/forms';
import { MaterialModule } from '@angular/material';

// angular flex-layout module
import { FlexLayoutModule } from '@angular/flex-layout';


@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    // material design
    MaterialModule.forRoot(),

    // flex layout
    FlexLayoutModule.forRoot(),
  ] ...

In package.json :

  "dependencies": {
    "@angular/common": "2.3.0",
    "@angular/compiler": "2.3.0",
    "@angular/core": "2.3.0",
    "@angular/flex-layout": "2.0.0-beta.1",
    "@angular/forms": "2.3.0",
    "@angular/http": "2.3.0",
    "@angular/material": "2.0.0-beta.1",
    "@angular/platform-browser": "2.3.0",
    "@angular/platform-browser-dynamic": "2.3.0",
...

In my explorer :

selection_021

Do you have a solution to my problem? Thank you for your help.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 2
Comments: 20 (8 by maintainers)

Most upvoted comments

@christophechevalier - Yeah, the gap between what we can do OSS and what is applicable to the projects we are building professionally is hard to bridge. There is a big difference between something with an app.component and something with 100 components, i’m in the same boat.

As this little endeavor would also be beneficial to me professionally, i’m happy to give you write access to my little cli playground and then adding a level or real world complexity in an attempt to recreate the issue.

Short of being able to dig through code or a bunch of stack traces, the above is the only path I can think of that has a remote chance of highlighting whatever the issue is.

joshwiens on Jan 3, 2017