You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the example. I've just tried it and works good, but the Frontend.Angular fails on production build:
ng build --prod
ERROR in Error encountered resolving symbol values statically. Calling function 'ɵmakeDecorator', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol Injectable in ..../no
de_modules/ng2-adal/node_modules/@angular/core/core.d.ts, resolving symbol ɵe in ..../node_modules/ng2-adal/node_modules/@angular/core/core.d.ts, resolving symbol ɵe in ..../node_modules/ng2-adal/node_modules/@angular/core/core.d
.ts
Do you have any idea how to fix it?
P.S. the error disappear if I switch off aot (>> ng build --prod --aot=false), but it's not the appropriate solution
Thanks,
Sujit
The text was updated successfully, but these errors were encountered:
The error you are describing is in the library I'm using: ng2-adal. There is issue reported: sureshchahal/angular2-adal#23 but the library wasn't updated for few months.
Hi.
Thank you for the example. I've just tried it and works good, but the Frontend.Angular fails on production build:
ERROR in Error encountered resolving symbol values statically. Calling function 'ɵmakeDecorator', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol Injectable in ..../no
de_modules/ng2-adal/node_modules/@angular/core/core.d.ts, resolving symbol ɵe in ..../node_modules/ng2-adal/node_modules/@angular/core/core.d.ts, resolving symbol ɵe in ..../node_modules/ng2-adal/node_modules/@angular/core/core.d
.ts
Do you have any idea how to fix it?
P.S. the error disappear if I switch off aot (>> ng build --prod --aot=false), but it's not the appropriate solution
Thanks,
Sujit
The text was updated successfully, but these errors were encountered: