AOT compilation fails about angular-pipes

[fknop]

What version of ngc are you using ? I tried a few days ago I didn't have any issues.

[aegyed91]

"@angular/compiler": "2.3.0",
"@angular/compiler-cli": "2.3.0",

[fknop]

Can you try with 2.3.1 ?

[aegyed91]

Got the same result with (double checked the node_module to make sure npm isnt loading the cached version):

    "@angular/common": "^2.3.1",
    "@angular/compiler": "^2.3.1",
    "@angular/compiler-cli": "^2.3.1",
    "@angular/core": "^2.3.1",
    "@angular/forms": "^2.3.1",
    "@angular/http": "^2.3.1",
    "@angular/platform-browser": "2.3.1",
    "@angular/platform-browser-dynamic": "2.3.1",
    "@angular/router": "3.3.1",
    "@angular/tsc-wrapped": "^0.5.0",
    "angular-pipes": "^5.5.0",

I think the error is caused because the lack of a metadata.json file, dougludlow/ng2-bs3-modal#105 (comment). But not sure are all.

Is it working on your side?

[fknop]

Did it work with the previous versions ? 5.4.0 or 5.3.0 ?

[aegyed91]

I dont know, havent tried it for a long time.

[fknop]

I'm busy I won't be able to try it today. If not tonight, I'll try tomorrow.

[aegyed91]

Alright, if i get to the end of my tasks today and still got some time left from work time ill try to fix it as well

[aegyed91]

Btw it seems you also generate the metadata files from what ngc feeds from.

Also compared your build files to some other ng2 modules i use. The only difference i recognized is: only ur files contains index.suffix.extension. No other project uses index files. Maybe this doesnt matter at all, maybe it does. (some weird module resolution option)

It is not much help i know. 💃

[fknop]

Just tried, it compiles with ngc 2.3.1 and angular-pipes 5.5.0

[aegyed91]

I wanted to create a reproduction repo but the aot compilation ran down perfectly there.

It is really weird why i keep getting Unexpected value 'NgPipesModule' imported by the module 'AppM', will further debug it. Sorry for tripping you with a non-existed issue.

[fknop]

No problem.

Check this comment. angular/angular#11438 (comment).
I remember having the issue, but it was in JIT mode.