Mateusz Kornecki

Hi @EoleDev, thanks for reaching out to us! To make it work you could save the chart reference and then use it to call the `chart.destroy()` method. For the future,...

Then you could try another approach. You can create a ref to the `highcharts-chart` component using the `@ViewChild` and then call its `ngOnDestroy()` method. Then to recreate the chart you...

Then let's combine both solutions - destroy the chart using chart reference from the callback function (no the component one), and reset the component's chart object to allow chart's recreation....

@zChanges Hello, Unfortunately for now `highcharts-angular` doesn't support such behavior. The only thing that could be returned there is a number, string, or string containing a valid HTML element. The...

@zChanges I thought about it for a while and it seems that I was wrong. You can achieve such behavior using Angular CDK portals. **Live demo:** https://stackblitz.com/edit/highcharts-angular-portal-usage?file=src/app/app.component.ts **References:** https://material.angular.io/cdk/portal/overview

Closing since the issue is resolved. The demo of the portal's usage will be added in the upcoming wrapper release.

You can find a detailed explanation below: > > Code in `index.js` runs at twice. First run is done in an environment that lacks `window` (server side) and causes Highcharts...

I cloned your repository. It seems that the fix that I suggested previously won't be that straightforward that I thought. I will try to fix that from the wrapper level...