-
Notifications
You must be signed in to change notification settings - Fork 110
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
New version 2.2.3 is not compatible with the current stable version of Angular (v13.2.0) #282
Comments
I'm also getting an error.. |
I am also getting the same error and that's why I downgraded the version to "angular-google-charts": "^2.2.2", |
I tried with Angular 12, downgraded it but when added the module, I got the same error. |
@situlindia change |
Thanks a lot. It's now working :) |
Frankly speaking, they should provide some example code, otherwise, it is too tough to integrate the chart. For the Maximum time, I am getting errors with input data. Can anyone send me a good example of a line and donut chart that has been implemented with this package? |
Currently, no version is working with Angular 13.x |
Dang. I would love to try your package
…On Wed, Aug 24, 2022, 2:55 AM Florian Buchner ***@***.***> wrote:
Currently, no version is working with Angular 13.x
Version 2.2.2 works only with Angular 12.x
Version 2.2.3 has the error described by @situlindia
<https://github.com/situlindia>
—
Reply to this email directly, view it on GitHub
<#282 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVAIY7RC222H5XQVWKDYJTV2XPPRANCNFSM537T73HQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm sorry for the trouble. We were unaware that Angular requires packages to be compiled with the minimum supported version of Angular. We've reverted version 2 to Angular 12 and will release a new major version supporting Angular 16+ in the upcoming days. |
The new version 2.2.3 is not compatible with the current stable version of Angular (v13.2.0).
Getting the below error during ng serve
The text was updated successfully, but these errors were encountered: