@besaitech/ng-design-system 0.0.67 → 0.0.69

package/README.md

@@ -205,6 +205,19 @@ Import names are the `Sl…` classes; the markup selectors are `sds-…`.
 | `SdsSidebar` + `SdsNavGroup` + `SdsNavItem` | `<sds-sidebar>` … | Collapsible nav rail; collapse state via root-provided `SidebarStore`; items render `routerLink` or `<button>` |
 
 **Charts** (D3 does the maths, Angular renders the SVG, so they are OnPush, SSR-safe and themed by tokens)
+— a **secondary entry point**, `@besaitech/ng-design-system/charts`:
+
+```ts
+import { SdsLineChart, SdsKpi, SdsChartSeries } from '@besaitech/ng-design-system/charts'; // components + chart data types
+import { provideSdsCharts, SdsChartLabels } from '@besaitech/ng-design-system';            // config + strings (root)
+```
+
+The root entry is ONE module: whatever an app uses from it anywhere — even on a lazy route — lands in
+the app's initial chunk. Keeping the charts (and d3) in their own entry lets the bundler leave them in
+the lazy chunk of the page that draws them. The configuration (`provideSdsCharts`, `SDS_CHART_CONFIG`,
+`SdsChartConfig`, `SdsChartLabels`, `SDS_CHART_LABELS_EN` and the label text types) stays in the root —
+it is tiny and d3-free — so `app.config` can provide it eagerly without pulling the charts in. Since
+0.0.68 the root no longer re-exports the chart components or chart types.
 
 | Component | Selector | Notes |
 | --- | --- | --- |