-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
p-chart: angular 17 chart.js integration errors #14258
Comments
I am also facing a similar issue with Chart.JS 4.4.1 when running Angular 17.0.4 |
I am also facing a similar issue
|
I've now ran into this same issue, however, I don't think it's actually a PrimeNG issue. If you install chart.js via If you instead download the Are all of you using Node 20? I am and that's where I'm encountering this issue. Update I tried older versions of Node as well and it still happens. Very odd. |
I change in angular.json to it work fine |
En mi caso: |
fixed/closed |
Describe the bug
Adding chart.js to now default Angular 17 project with standalone components and SSR according to PrimeNG documentation causes errors. I was thinking it was something akin to errors I was receiving while adding NGXS implementation with Angular 17, having to do with SSR and requiring the providers in app.config.ts and app.config.server.ts because the server is not providing what the client is expecting?
I also installed npm i @types/chart.js
Adding the following to angular.json causes an app breaking error in the browser
Receiving the following error
Upon changing angular.json to the following, non app breaking error occurs, only displaying in vsc terminal
This is the error received
Environment
Reproducer
No response
Angular version
17.0.1
PrimeNG version
17.0.0-beta.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
No response
Steps to reproduce the behavior
Add chart.js to angular/PrimeNG project as instructed in PrimeNG docs 17.0.0-beta.1
Expected behavior
PrimeNG Angular17 chart.js integration without errors and app breaking errors
The text was updated successfully, but these errors were encountered: