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
The app has been working great for 2 weeks then last night I updated my OSX to Sierra. Everything worked this morning till I decided to update my angular-cli to 1.0.0-beta.16. At thi spoint the app broke and was giving me errors when trying to load images to the page from the assets folder.
I spent hours confirming files were indeed in the correct path and then rolled back my version of angular-cli, node, and npm to many different versions and combinations to clear the problem.
At this point I cleared the original errors but instead of getting the app to load now it gives me a new set of errors. It appears it has to do with the ng-charts the dashboard is using. I have not changed anything from the original code on the dashboard. I uninstalled node and npm from my machine and reinstalled it to latest. I cloned a new version of CoreUI-Free-Bootstrap-Admin-Template and npm installed it with
angular-cli: 1.0.0-beta.17
node: 6.7.0
os: darwin x64
npm: 3.10.3
But at this point I am still dealing with the problem pertaining to ng-charts. Any help or ideas on what I can do from here would be appreciated. I have been hacking away at these errors for 12 hours today and I am out of troubleshooting ideas. Reinstalling the app and getting the same errors as my app that has been in development for 2 weeks tells me that it has to do with the most updated versions of node npm and angular-cli breaking with the code in the CoreUI Template.
Here is a chunk of my error log.
zone.js:355Unhandled Promise rejection: Template parse errors:
Can't bind to 'datasets' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'datasets' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("iv>
<base-chart class="chart" [ERROR ->][datasets]="lineChart1Data" [labels]="lineChart1Labels" [options]="lineChart1Options" [colors]="lineC"): DashboardComponent@19:46
Can't bind to 'labels' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'labels' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("ss="chart-wrapper p-x-1">
<base-chart class="chart" [datasets]="lineChart1Data" [ERROR ->][labels]="lineChart1Labels" [options]="lineChart1Options" [colors]="lineChart1Colours" [legend]="line"): DashboardComponent@19:74
Can't bind to 'options' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'options' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
(" <base-chart class="chart" [datasets]="lineChart1Data" [labels]="lineChart1Labels" [ERROR ->][options]="lineChart1Options" [colors]="lineChart1Colours" [legend]="lineChart1Legend" [chartType]="l"): DashboardComponent@19:102
Can't bind to 'colors' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'colors' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("class="chart" [datasets]="lineChart1Data" [labels]="lineChart1Labels" [options]="lineChart1Options" [ERROR ->][colors]="lineChart1Colours" [legend]="lineChart1Legend" [chartType]="lineChart1Type" (chartHover)="c"): DashboardComponent@19:132
Can't bind to 'legend' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'legend' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("eChart1Data" [labels]="lineChart1Labels" [options]="lineChart1Options" [colors]="lineChart1Colours" [ERROR ->][legend]="lineChart1Legend" [chartType]="lineChart1Type" (chartHover)="chartHovered($event)" (chartCl"): DashboardComponent@19:161
Can't bind to 'chartType' since it isn't a known property of 'base-chart'.
If 'base-chart' is an Angular component and it has 'chartType' input, then verify that it is part of this module.
If 'base-chart' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("hart1Labels" [options]="lineChart1Options" [colors]="lineChart1Colours" [legend]="lineChart1Legend" [ERROR ->][chartType]="lineChart1Type" (chartHover)="chartHovered($event)" (chartClick)="chartClicked($event)"
"): DashboardComponent@19:189
The text was updated successfully, but these errors were encountered:
The app has been working great for 2 weeks then last night I updated my OSX to Sierra. Everything worked this morning till I decided to update my angular-cli to 1.0.0-beta.16. At thi spoint the app broke and was giving me errors when trying to load images to the page from the assets folder.
I spent hours confirming files were indeed in the correct path and then rolled back my version of angular-cli, node, and npm to many different versions and combinations to clear the problem.
At this point I cleared the original errors but instead of getting the app to load now it gives me a new set of errors. It appears it has to do with the ng-charts the dashboard is using. I have not changed anything from the original code on the dashboard. I uninstalled node and npm from my machine and reinstalled it to latest. I cloned a new version of CoreUI-Free-Bootstrap-Admin-Template and npm installed it with
angular-cli: 1.0.0-beta.17
node: 6.7.0
os: darwin x64
npm: 3.10.3
But at this point I am still dealing with the problem pertaining to ng-charts. Any help or ideas on what I can do from here would be appreciated. I have been hacking away at these errors for 12 hours today and I am out of troubleshooting ideas. Reinstalling the app and getting the same errors as my app that has been in development for 2 weeks tells me that it has to do with the most updated versions of node npm and angular-cli breaking with the code in the CoreUI Template.
Here is a chunk of my error log.
The text was updated successfully, but these errors were encountered: