-
Notifications
You must be signed in to change notification settings - Fork 82
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
Warning In angular 10 #92
Comments
This issue can be removed by adding
|
@IsaacSomething, this will only suppress the warning and not actually fix the issue causing this warning. |
That's because this lib is depending on the CommonJS module instead of the ESM (surprise) I see that they changed the import from the ESM to the min version, and later removed the deep import to get rid of the ivy warning. See #79 |
@stefanolsenn The ESM module caused issues in all libraries (react/vue/angular) because of the way it was generated. |
What issues are we talking about here? |
There is a 3rd party library called svg.js being bundled inside. |
Any news on this? Seems like the svg.js being exposed is an issue that could be solved. As Angular moves pretty fast, it would be great to not have optimization bailouts in the current versions. |
Any updates on this? apexcharts is 25% of my apps bundle size. |
Any update on this? Is this a time-consuming bug to fix? |
Any update on this issue? I just updated from Angular 13 (everything was ok) to Angular 14 and this warning started to appear. |
Seeing this as well with Angular 16 :/ |
I found that manually adding: "es2020": "dist/apexcharts.esm.js", to the So to get this fixed we would need to get this field added to the apexcharts library. Here is the order that Angular uses to find the entry point in a package: EDIT: It does come with this warning if you run
|
When I start the angular 10 app I am getting below mentioned warning
ng-apexcharts__ivy_ngcc__fesm2015 g-apexcharts.js depends on 'apexcharts'. CommonJS or AMD dependencies can cause optimization bailouts.
The text was updated successfully, but these errors were encountered: