Skip to content
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

module do not works after build #59

Closed
ptsydzik-zz opened this issue Aug 17, 2016 · 1 comment
Closed

module do not works after build #59

ptsydzik-zz opened this issue Aug 17, 2016 · 1 comment

Comments

@ptsydzik-zz
Copy link

ptsydzik-zz commented Aug 17, 2016

then i use this module in local build its works fine but after build using sistemjs i got errors

lib-2f3a00f50a.js:7 Unhandled Promise rejection: Template parse errors:
Can't bind to 'item' since it isn't a known property of 'simple-notification'.
1. If 'simple-notification' is an Angular component and it has 'item' input, then verify that it is part of this module.
2. If 'simple-notification' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
 ("<simple-notification
                *ngFor="let a of notifications; let i = index"
                [ERROR ->][item]="a"
                [timeOut]="timeOut"
                [clickToClose]="clickToClose"
"): a@4:16
Can't bind to 'timeOut' since it isn't a known property of 'simple-notification'.
1. If 'simple-notification' is an Angular component and it has 'timeOut' input, then verify that it is part of this module.
2. If 'simple-notification' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
 ("          *ngFor="let a of notifications; let i = index"
                [item]="a"
                [ERROR ->][timeOut]="timeOut"
                [clickToClose]="clickToClose"
                [maxLength]="maxLen"): a@5:16

all configuration and setup is done as described in example.
Am I missing something or am I doing something wrong?

@ptsydzik-zz
Copy link
Author

issue solved by set mangle options to false in gulp config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant