jkasperbl opened a new issue, #16834: URL: https://github.com/apache/echarts/issues/16834
### Version 5.3.2 ### Link to Minimal Reproduction https://stackblitz.com/edit/github-1mzjky-bfluyv?file=src/app/app.module.ts ### Steps to Reproduce Open the StackBlitz link above and a simple line chart will render using a full Echarts build. The issue occurs if you modify `app.module.ts` to us the custom Echarts treeshaking build instead -- the chart will no longer render, despite no error message in the console. ### Current Behavior With the current code in the StackBlitz link provided above, my sample line chart renders correctly. However, this is using a "full" echarts import which you can see in app.module.ts: ``` NgxEchartsModule.forRoot({ echarts: () => import('echarts' as const) }) ``` If you comment out that line and uncomment the line above, it will instead use my attempt at a custom build: ``` NgxEchartsModule.forRoot({ echarts }) ``` Although no errors are present in the JavaScript console, the chart no longer renders. ### Expected Behavior The chart should render with a custom treeshaking build. ### Environment ```markdown - OS: Windows 11 - Browser: Edge - Framework: Angular ``` ### Any additional comments? As far as I can tell, I have imported all of the necessary components required for such a simple example --I would think `* from echarts/core`, `LineChart`, and `CanvasRenderer' are all that's needed, but it seems likely there's something else I'm missing that I'm not aware of. ``` import * as echarts from 'echarts/core'; import { LineChart } from 'echarts/charts'; import { GridComponent, LegendComponent, TitleComponent, ToolboxComponent, TooltipComponent, } from 'echarts/components'; import { CanvasRenderer } from 'echarts/renderers'; import { NgxEchartsModule } from 'ngx-echarts'; echarts.use([ CanvasRenderer, GridComponent, LegendComponent, LineChart, TitleComponent, ToolboxComponent, TooltipComponent, ]); ``` Any help would be greatly appreciated in figuring this out. It's possible that this issue is with the ngx-echarts library rather than core Echarts, but since most of the imports are directly from the core package I think that's unlikely. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org For additional commands, e-mail: dev-h...@echarts.apache.org
