Warning In angular 10

[yeshwanthmn]

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.

[IsaacSomething]

This issue can be removed by adding "apexcharts" to the allowedCommonJsDependencies in your angular.json file

"architect": {
        "build": {
             "options": {
                  "allowedCommonJsDependencies":

[j-a-h-i-r]

@IsaacSomething, this will only suppress the warning and not actually fix the issue causing this warning.

[stefanolsenn]

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 @junedchhipa Maybe you could clarify a bit on that decision? I would rather silence the deep import warning, than my bundle size increases.

[junedchhipa]

@stefanolsenn The ESM module caused issues in all libraries (react/vue/angular) because of the way it was generated. I haven't found a fix for that and hence it was removed.

[stefanolsenn]

What issues are we talking about here?

[junedchhipa]

There is a 3rd party library called svg.js being bundled inside. Instead of the main ApexCharts being exposed, SVG was exposed from the ESM module.

[stashaway]

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.

[MNorgren]

Any updates on this? apexcharts is 25% of my apps bundle size.

[AmirSavand]

Any update on this? Is this a time-consuming bug to fix?

[muhammadtayab257]

In my case, I was facing the same issue I have added these lines in my angular.json file => "allowedCommonJsDependencies": ["apexcharts"], and it works for me My angular Version 14.0.0 and apex chart version 3.35.3

[AmirSavand]

@muhammadtayab257 That's just ignoring the warning.

[VitorBarleta]

Any update on this issue? I just updated from Angular 13 (everything was ok) to Angular 14 and this warning started to appear.

[rtpHarry]

Seeing this as well with Angular 16 :/