@ojiepermana/angular 21.2.4 → 21.3.3

package/README.md

@@ -16,8 +16,13 @@ Install the published package into a consumer Angular workspace with Angular
 CLI so the required peer dependencies are added to the app's `package.json`
 and installed in the same flow:
 
+In the consumer snippets below, `@your-scope/angular` means the package name
+your workspace actually installs. Replace it consistently with the published
+target you use, for example `@ojiepermana/angular`, `@edsis/angular`, or
+another branded alias such as `@etos/angular`.
+
 ```bash
-ng add @ojiepermana/angular
+ng add @your-scope/angular
 ```
 
 The library requires Tailwind CSS `^4.3.0`. If the consumer workspace does
@@ -27,7 +32,7 @@ from the published `peerDependencies`.
 When updating the library later, use Angular CLI as well:
 
 ```bash
-ng update @ojiepermana/angular
+ng update @your-scope/angular
 ```
 
 The package ships `ng-add` and `ng-update` metadata so Angular and RxJS
@@ -38,21 +43,153 @@ add` directly, peer dependency installation falls back to the package
 manager's own behavior. In that flow, install Tailwind manually as well:
 
 ```bash
-bun add @ojiepermana/angular tailwindcss@^4.3.0
+bun add @your-scope/angular tailwindcss@^4.3.0
 ```
 
 Consumer app styles should import the library theme, Tailwind, and the
 Tailwind bridge in this order:
 
 ```css
-@import '@ojiepermana/angular/theme/styles';
+@import '@your-scope/angular/theme/styles';
+@import 'tailwindcss';
+@import '@your-scope/angular/theme/tailwind/theme.css';
+```
+
+## Theme entrypoint
+
+The shared theme runtime ships through `@your-scope/angular/theme`, with
+granular deep-import surfaces available at `@your-scope/angular/theme/services`,
+`@your-scope/angular/theme/provider`, and `@your-scope/angular/theme/token`.
+The CSS assets stay available through `@your-scope/angular/theme/styles` and
+`@your-scope/angular/theme/tailwind/theme.css`.
+
+```ts
+import { provideMaterialTheme, withMaterialDefaults } from '@your-scope/angular/theme';
+```
+
+```css
+@import '@your-scope/angular/theme/styles';
 @import 'tailwindcss';
-@import '@ojiepermana/angular/theme/tailwind/theme.css';
+@import '@your-scope/angular/theme/tailwind/theme.css';
 ```
 
+For contributors working in this repository, the theme entrypoint source is
+split into runtime APIs under [`projects/angular/theme/services/src/lib`](theme/services/src/lib),
+[`projects/angular/theme/provider/src/lib`](theme/provider/src/lib),
+[`projects/angular/theme/token/src/lib`](theme/token/src/lib), and stylesheet
+assets under [`projects/angular/theme/css`](theme/css).
+The stylesheet sources are grouped into `foundation/`, `variants/`, and
+`integrations/`. Local entrypoint notes live in
+[`projects/angular/theme/README.md`](theme/README.md).
+
+To run the theme-only regression suite from the workspace root, use:
+
+```bash
+bun run test:theme
+```
+
+## Breaking change migration
+
+Granular secondary entrypoints are now the required component and navigation
+surface. If your app previously imported from the removed
+`@your-scope/angular/component` or `@your-scope/angular/navigation` barrels,
+migrate in this order:
+
+1. Confirm the package root you install in the consumer app. Keep that same
+   root in every `ng add`, `ng update`, stylesheet import, and TypeScript
+   import.
+2. Replace broad barrel imports such as `@your-scope/angular/component` with
+   the smallest matching subpath, for example
+   `@your-scope/angular/component/button` or
+   `@your-scope/angular/component/dropdown-menu`.
+3. Replace removed navigation imports such as `@your-scope/angular/navigation`
+   with the matching navigation subpath, for example
+   `@your-scope/angular/navigation/sidebar`,
+   `@your-scope/angular/navigation/topbar`,
+   `@your-scope/angular/navigation/service`, or
+   `@your-scope/angular/navigation/types`.
+4. Update any internal helper imports to their new granular subpaths as well,
+   including utilities such as `@your-scope/angular/component/utils`.
+5. Update schematic commands in the same way. The package name before the
+   colon must match the installed target.
+
+Example migration:
+
+```ts
+import { ButtonComponent } from '@your-scope/angular/component/button';
+import { DropdownMenuComponent } from '@your-scope/angular/component/dropdown-menu';
+import { SidebarComponent } from '@your-scope/angular/navigation/sidebar';
+import { NavigationService } from '@your-scope/angular/navigation/service';
+import { UiNavIconComponent } from '@your-scope/angular/navigation/icon';
+```
+
+## Granular imports for production builds
+
+Prefer the smallest subpath that matches the primitives you actually use,
+especially in Native Federation or other shared-chunk builds. Every component
+now ships only through its matching granular subpath, for example
+`@your-scope/angular/component/date-picker`,
+`@your-scope/angular/component/dropdown-menu`, and
+`@your-scope/angular/component/tooltip`.
+
+```ts
+import { AvatarComponent, AvatarFallbackComponent, AvatarImageComponent } from '@your-scope/angular/component/avatar';
+import { ButtonComponent } from '@your-scope/angular/component/button';
+import { PopoverContentDirective, PopoverTriggerDirective } from '@your-scope/angular/component/popover';
+import { cn } from '@your-scope/angular/component/utils';
+import { UiNavIconComponent } from '@your-scope/angular/navigation/icon';
+```
+
+`@your-scope/angular/component` and `@your-scope/angular/navigation` aggregate
+barrels have been removed. Consumers should use granular
+`@your-scope/angular/component/<slug>` and
+`@your-scope/angular/navigation/<part>` imports.
+
+Navigation now follows the same granular pattern:
+`@your-scope/angular/navigation/types`,
+`@your-scope/angular/navigation/service`,
+`@your-scope/angular/navigation/sidebar`,
+`@your-scope/angular/navigation/topbar`,
+`@your-scope/angular/navigation/item`,
+`@your-scope/angular/navigation/icon`, and
+`@your-scope/angular/navigation/demo-data`.
+
+The same subpaths are preserved for branded packages. For example, a consumer
+built from the EDSIS release uses:
+
+```ts
+import { ButtonComponent } from '@edsis/angular/component/button';
+import { cn } from '@edsis/angular/component/utils';
+import { UiNavIconComponent } from '@edsis/angular/navigation/icon';
+```
+
+To verify the generated package still publishes smaller entrypoints after a
+build, run:
+
+```bash
+bun run build
+bun run report:entrypoints -- --check
+```
+
+The size report validates that every granular component and navigation
+entrypoint resolves to its own module and that the removed `./component` and
+`./navigation` parent barrels do not return in the published exports.
+
 ## Navigation primitives
 
-`@ojiepermana/angular/navigation` exports the shared sidebar and topbar building blocks used by the demo shells. The vertical navigation selector is now `sidebar` and the projected sidebar slots use `sidebar-header` and `sidebar-footer`.
+The navigation library now publishes only granular child entrypoints, so each
+part can be consumed independently.
+
+```ts
+import { SidebarComponent } from '@your-scope/angular/navigation/sidebar';
+import { TopbarComponent } from '@your-scope/angular/navigation/topbar';
+import { NavigationService } from '@your-scope/angular/navigation/service';
+import type { NavigationItem, SidebarAppearance } from '@your-scope/angular/navigation/types';
+import { UiNavIconComponent } from '@your-scope/angular/navigation/icon';
+```
+
+The vertical navigation selector is now `sidebar` and the projected sidebar
+slots use `sidebar-header` and `sidebar-footer`.
 
 ```html
 <sidebar [ariaLabel]="'Primary'" [appearance]="'default'">
@@ -70,9 +207,9 @@ SDK config file under `config/sdk.config.json` and generate an Angular SDK direc
 schematics:
 
 ```bash
-ng generate @ojiepermana/angular:sdk-init
+ng generate @your-scope/angular:sdk-init
 # edit config/sdk.config.json
-ng generate @ojiepermana/angular:sdk
+ng generate @your-scope/angular:sdk
 ```
 
 The main consumer flow is: create `config/sdk.config.json`, adjust the OpenAPI
@@ -83,8 +220,8 @@ If you want short script aliases in the consumer app's `package.json`, add:
 ```json
 {
   "scripts": {
-    "gen:sdk:init": "ng generate @ojiepermana/angular:sdk-init",
-    "gen:sdk": "ng generate @ojiepermana/angular:sdk"
+    "gen:sdk:init": "ng generate @your-scope/angular:sdk-init",
+    "gen:sdk": "ng generate @your-scope/angular:sdk"
   }
 }
 ```
@@ -95,8 +232,8 @@ ships the compiled schematic runtime.
 Common follow-up options:
 
 ```bash
-ng generate @ojiepermana/angular:sdk-init --path=config/my-sdk.config.json
-ng generate @ojiepermana/angular:sdk --config=config/my-sdk.config.json --dry-run
+ng generate @your-scope/angular:sdk-init --path=config/my-sdk.config.json
+ng generate @your-scope/angular:sdk --config=config/my-sdk.config.json --dry-run
 ```
 
 ## Code scaffolding
@@ -123,6 +260,12 @@ bun run build
 
 This command will compile your project, and the build artifacts will be placed in the `dist/` directory.
 
+To inspect the generated entrypoint sizes after a build, run:
+
+```bash
+bun run report:entrypoints
+```
+
 ### Publishing the Library
 
 Publish the scoped package to the public npm registry from the workspace root.

package/component/accordion/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-accordion.mjs",
+  "typings": "../../types/ojiepermana-angular-component-accordion.d.ts"
+}

package/component/alert/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-alert.mjs",
+  "typings": "../../types/ojiepermana-angular-component-alert.d.ts"
+}

package/component/alert-dialog/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-alert-dialog.mjs",
+  "typings": "../../types/ojiepermana-angular-component-alert-dialog.d.ts"
+}

package/component/aspect-ratio/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-aspect-ratio.mjs",
+  "typings": "../../types/ojiepermana-angular-component-aspect-ratio.d.ts"
+}

package/component/avatar/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-avatar.mjs",
+  "typings": "../../types/ojiepermana-angular-component-avatar.d.ts"
+}

package/component/badge/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-badge.mjs",
+  "typings": "../../types/ojiepermana-angular-component-badge.d.ts"
+}

package/component/breadcrumb/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-breadcrumb.mjs",
+  "typings": "../../types/ojiepermana-angular-component-breadcrumb.d.ts"
+}

package/component/button/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-button.mjs",
+  "typings": "../../types/ojiepermana-angular-component-button.d.ts"
+}

package/component/button-group/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-button-group.mjs",
+  "typings": "../../types/ojiepermana-angular-component-button-group.d.ts"
+}

package/component/calendar/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-calendar.mjs",
+  "typings": "../../types/ojiepermana-angular-component-calendar.d.ts"
+}

package/component/card/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-card.mjs",
+  "typings": "../../types/ojiepermana-angular-component-card.d.ts"
+}

package/component/carousel/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-carousel.mjs",
+  "typings": "../../types/ojiepermana-angular-component-carousel.d.ts"
+}

package/component/chart/README.md

@@ -0,0 +1,249 @@
+# Chart
+
+Angular chart primitives and chart families inspired by shadcn Chart.
+
+In this repository, shadcn's single Chart page maps to the dedicated `/ui/chart/*` demo route group so each chart family can keep focused, production-like examples without forcing everything into one `/ui/shadcn/chart` page.
+
+Use Chart for dashboards, KPI cards, trend comparisons, radial summaries, and interactive data views where one shared config should drive labels, colors, legends, and tooltip copy.
+
+## Installation
+
+```bash
+bun add @ojiepermana/angular
+npm install @ojiepermana/angular
+```
+
+## Import
+
+Import shared primitives from the chart root entrypoint, then import the concrete chart family from its granular subpath.
+
+```ts
+import {
+  ChartAxisX,
+  ChartAxisY,
+  ChartContainer,
+  ChartGrid,
+  ChartLegend,
+  ChartTooltip,
+  type ChartConfig,
+} from '@ojiepermana/angular/component/chart';
+import { BarChart } from '@ojiepermana/angular/component/chart/bar';
+```
+
+### Supported chart entrypoints
+
+| Import path                                    | Selector           | Best for                                                          |
+| ---------------------------------------------- | ------------------ | ----------------------------------------------------------------- |
+| `@ojiepermana/angular/component/chart/bar`     | `ui-bar-chart`     | grouped, stacked, horizontal, active, and mixed-color bar layouts |
+| `@ojiepermana/angular/component/chart/line`    | `ui-line-chart`    | trends, comparisons, and zoomable time-series lines               |
+| `@ojiepermana/angular/component/chart/area`    | `ui-area-chart`    | filled trend bands, stacked areas, and expanded percent views     |
+| `@ojiepermana/angular/component/chart/pie`     | `ui-pie-chart`     | part-to-whole slices and donut charts                             |
+| `@ojiepermana/angular/component/chart/radar`   | `ui-radar-chart`   | multi-axis performance comparisons                                |
+| `@ojiepermana/angular/component/chart/radial`  | `ui-radial-chart`  | progress rings, radial comparisons, and center-metric summaries   |
+| `@ojiepermana/angular/component/chart/scatter` | `ui-scatter-chart` | XY correlation plots and point clouds                             |
+
+## Composition
+
+The Angular structure keeps the same high-level idea as shadcn Chart: define a shared chart config once, then compose a specific chart type with optional grid, axis, tooltip, legend, and center content.
+
+```text
+ui-chart-container
+├── ui-bar-chart | ui-line-chart | ui-area-chart | ui-scatter-chart
+│   ├── svg:g[ui-chart-grid]
+│   ├── svg:g[ui-chart-axis-x]
+│   ├── svg:g[ui-chart-axis-y]
+│   └── svg:g[ui-chart-crosshair] / svg:g[ui-chart-brush] (optional)
+├── ui-pie-chart | ui-radial-chart | ui-radar-chart
+│   └── ui-pie-center | ui-radial-center (optional)
+├── ui-chart-tooltip
+├── ui-chart-legend
+└── ui-chart-zoom-controls (optional)
+```
+
+All child primitives read dimensions, series metadata, and scoped color tokens from `ui-chart-container`.
+
+## Basic usage
+
+Start with a readonly `ChartConfig`, keep the dataset in any shape that makes sense for your feature, and map the chart to the relevant keys.
+
+```ts
+const trafficChartConfig = {
+  desktop: { label: 'Desktop', color: 'var(--chart-1)' },
+  mobile: { label: 'Mobile', color: 'var(--chart-2)' },
+} satisfies ChartConfig;
+
+const trafficData = [
+  { month: 'January', desktop: 186, mobile: 80 },
+  { month: 'February', desktop: 305, mobile: 200 },
+  { month: 'March', desktop: 237, mobile: 120 },
+  { month: 'April', desktop: 73, mobile: 190 },
+  { month: 'May', desktop: 209, mobile: 130 },
+  { month: 'June', desktop: 214, mobile: 140 },
+];
+```
+
+```html
+<div class="w-full max-w-3xl">
+  <ui-chart-container [config]="trafficChartConfig" chartId="traffic-overview">
+    <ui-bar-chart [data]="trafficData" xKey="month">
+      <svg:g ui-chart-grid></svg:g>
+      <svg:g ui-chart-axis-x></svg:g>
+      <svg:g ui-chart-axis-y></svg:g>
+    </ui-bar-chart>
+    <ui-chart-tooltip [data]="trafficData" xKey="month" />
+    <ui-chart-legend />
+  </ui-chart-container>
+</div>
+```
+
+## Common patterns
+
+### First chart flow
+
+The closest Angular equivalent to the upstream shadcn walkthrough is:
+
+1. Define your dataset.
+2. Define `ChartConfig` so labels and colors stay decoupled from the raw data.
+3. Wrap the chart in `ui-chart-container`.
+4. Add `svg:g[ui-chart-grid]`, axis directives, `ui-chart-tooltip`, and `ui-chart-legend` only where they add value.
+
+This keeps the chart family focused while still letting the shared primitives manage the common UI pieces.
+
+### Swapping chart families
+
+The same `ChartConfig` can back multiple chart families. In most cases you only swap the concrete chart import and the family-specific inputs.
+
+```ts
+import { AreaChart } from '@ojiepermana/angular/component/chart/area';
+import { LineChart } from '@ojiepermana/angular/component/chart/line';
+```
+
+- `ui-line-chart` adds inputs such as `curve`, `showDots`, and `showValueLabels`.
+- `ui-area-chart` adds `stacked`, `expanded`, `gradient`, and `curve`.
+- `ui-bar-chart` adds `orientation`, `variant`, `colorKey`, `activeKey`, and `activeValue`.
+
+### Pie and radial summaries
+
+For donut, pie, and radial progress layouts, use `nameKey` plus `valueKey` instead of `xKey`.
+
+```html
+<ui-chart-container [config]="browserConfig" aspect="aspect-square">
+  <ui-pie-chart
+    [data]="browserData"
+    nameKey="browser"
+    valueKey="visitors"
+    [seriesKeys]="browserSeriesKeys"
+    [innerRadius]="64">
+  </ui-pie-chart>
+  <ui-chart-tooltip [data]="browserData" xKey="browser" valueKey="visitors" indicator="dot" />
+  <ui-chart-legend />
+</ui-chart-container>
+```
+
+### Tooltip formatting
+
+`ui-chart-tooltip` is where most presentational customization lives.
+
+```html
+<ui-chart-tooltip
+  [data]="activityData"
+  xKey="date"
+  indicator="line"
+  labelKey="views"
+  [labelFormatter]="longDateFormatter"
+  [formatter]="compactNumberFormatter" />
+```
+
+Use `valueKey` for single-value radial and pie datasets, `hideLabel` when the card already provides the label context, and `indicator="none"` when you want a copy-first tooltip layout.
+
+### Per-row colors and active emphasis
+
+Use `colorKey` when the dataset itself carries a color token such as `fill`, and use `activeKey` plus `activeValue` when one category should be visually emphasized without rewriting the whole series config.
+
+## API reference
+
+### `ChartContainer`
+
+| Input     | Type             | Default          |
+| --------- | ---------------- | ---------------- |
+| `config`  | `ChartConfig`    | —                |
+| `aspect`  | `string`         | `'aspect-video'` |
+| `chartId` | `string \| null` | auto-generated   |
+
+`ChartConfig` is a readonly record of series keys to labels, icons, colors, or theme-aware light/dark color maps.
+
+```ts
+type ChartConfig = Readonly<
+  Record<
+    string,
+    {
+      label?: string;
+      icon?: Type<unknown>;
+      color?: string;
+      theme?: Readonly<Record<'light' | 'dark', string>>;
+    }
+  >
+>;
+```
+
+### Shared primitives
+
+| Part                     | Key inputs                                                                                               | Notes                                                           |
+| ------------------------ | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
+| `svg:g[ui-chart-grid]`   | none                                                                                                     | Adds cartesian grid lines behind bar, line, and area charts.    |
+| `svg:g[ui-chart-axis-x]` | `tickCount`, `tickLine`, `tickFormat`                                                                    | Categorical axis for cartesian layouts.                         |
+| `svg:g[ui-chart-axis-y]` | `tickCount`, `tickLine`, `tickFormat`                                                                    | Numeric axis for cartesian layouts.                             |
+| `ui-chart-tooltip`       | `data`, `xKey`, `valueKey`, `indicator`, `label`, `labelKey`, `labelFormatter`, `formatter`, `hideLabel` | Handles default tooltip layout plus custom template projection. |
+| `ui-chart-legend`        | none                                                                                                     | Renders toggle buttons for visible series.                      |
+| `ui-chart-zoom-controls` | none                                                                                                     | Pair with zoomable line and scatter views.                      |
+| `ui-pie-center`          | projected content                                                                                        | Centers labels or KPIs inside pie layouts.                      |
+| `ui-radial-center`       | projected content                                                                                        | Centers labels or KPIs inside radial layouts.                   |
+
+### Chart families
+
+| Selector           | Key inputs                                                                                          |
+| ------------------ | --------------------------------------------------------------------------------------------------- |
+| `ui-bar-chart`     | `data`, `xKey`, `orientation`, `variant`, `colorKey`, `activeKey`, `activeValue`, `showValueLabels` |
+| `ui-line-chart`    | `data`, `xKey`, `curve`, `showDots`, `dotRadius`, `showValueLabels`                                 |
+| `ui-area-chart`    | `data`, `xKey`, `stacked`, `expanded`, `gradient`, `curve`                                          |
+| `ui-pie-chart`     | `data`, `nameKey`, `valueKey`, `seriesKeys`, `innerRadius`, `activeIndex`, `activeOffset`           |
+| `ui-radar-chart`   | `data`, `axisKey`, `curve`, `levels`, `grid`, `showLabels`, `showDots`                              |
+| `ui-radial-chart`  | `data`, `nameKey`, `valueKey`, `seriesKeys`, `maxValue`, `showTrack`, `showValueLabels`             |
+| `ui-scatter-chart` | `data`, `xKey`, `yKey`, `sizeKey`, `seriesKey`, `xDomain`, `yDomain`                                |
+
+## Styling and theming
+
+- Prefer CSS variables such as `var(--chart-1)` and `var(--chart-2)` in `ChartConfig`. This matches the current shadcn guidance and the theme tokens shipped by this library.
+- `ui-chart-container` scopes generated `--color-<series>` variables to the chart instance, so tooltip rows, legends, and series shapes stay aligned.
+- Use `theme: { light, dark }` on a series config entry when the chart needs different values per color scheme.
+- Keep the parent container responsible for width, and use the `aspect` input when the default `aspect-video` does not match the layout.
+- Use `colorKey` only when the dataset should override per-series colors with a row-specific token such as `fill`.
+
+## Accessibility
+
+- Chart hosts expose an `aria-label` summary describing the chart type, category count, and visible series.
+- Interactive marks such as bars, dots, and slices are keyboard focusable where the layout supports activation.
+- `ui-chart-tooltip` includes a polite live region so changing categories can be announced to assistive technology.
+- `ui-chart-legend` uses native buttons with `aria-pressed` to reflect hidden and visible series state.
+- Keep surrounding card copy descriptive so the chart has enough context when read outside its visual layout.
+
+## Keyboard interactions
+
+- `Tab` reaches interactive bars, dots, slices, and legend toggle buttons.
+- `Enter` and `Space` trigger the same click behavior as pointer activation on interactive marks.
+- Focusing a supported data mark updates the shared active point so tooltip content stays reachable without hover.
+
+## Angular notes
+
+- Keep chart config objects readonly and signal-friendly. A top-level `const` or signal-backed computed config works well.
+- Every chart family must live inside `ui-chart-container`; that container provides dimensions, series visibility state, and scoped color variables to descendants.
+- Use an explicit `chartId` when multiple charts of the same family appear on one page or when tests need a stable selector.
+- The local shadcn mapping for Chart lives in the dedicated `/ui/chart` overview route with focused family demos under `/ui/chart/*`.
+
+## Source parity
+
+This Angular package follows the shadcn Chart information architecture and theming concepts, but it does not mirror the React API one-to-one.
+
+- shadcn uses Recharts components directly and layers `ChartTooltipContent` and `ChartLegendContent` around them.
+- This Angular library ships standalone chart families plus shared primitives, so you compose `ui-chart-container`, the relevant `ui-*-chart`, `ui-chart-tooltip`, and `ui-chart-legend` instead of wiring Recharts JSX.
+- The dedicated `/ui/chart/*` route group is the intentional local mapping for shadcn Chart in this repo; no duplicate `/ui/shadcn/chart` page is required.

package/component/chart/area/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-area.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-area.d.ts"
+}

package/component/chart/bar/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-bar.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-bar.d.ts"
+}

package/component/chart/line/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-line.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-line.d.ts"
+}

package/component/chart/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-chart.mjs",
+  "typings": "../../types/ojiepermana-angular-component-chart.d.ts"
+}

package/component/chart/pie/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-pie.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-pie.d.ts"
+}

package/component/chart/radar/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-radar.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-radar.d.ts"
+}

package/component/chart/radial/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-radial.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-radial.d.ts"
+}

package/component/chart/scatter/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../../fesm2022/ojiepermana-angular-component-chart-scatter.mjs",
+  "typings": "../../../types/ojiepermana-angular-component-chart-scatter.d.ts"
+}

package/component/checkbox/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-checkbox.mjs",
+  "typings": "../../types/ojiepermana-angular-component-checkbox.d.ts"
+}

package/component/collapsible/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-collapsible.mjs",
+  "typings": "../../types/ojiepermana-angular-component-collapsible.d.ts"
+}

package/component/combobox/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-combobox.mjs",
+  "typings": "../../types/ojiepermana-angular-component-combobox.d.ts"
+}

package/component/command/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-command.mjs",
+  "typings": "../../types/ojiepermana-angular-component-command.d.ts"
+}

package/component/context-menu/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-context-menu.mjs",
+  "typings": "../../types/ojiepermana-angular-component-context-menu.d.ts"
+}

package/component/date-picker/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-date-picker.mjs",
+  "typings": "../../types/ojiepermana-angular-component-date-picker.d.ts"
+}

package/component/dialog/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-dialog.mjs",
+  "typings": "../../types/ojiepermana-angular-component-dialog.d.ts"
+}

package/component/drawer/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-drawer.mjs",
+  "typings": "../../types/ojiepermana-angular-component-drawer.d.ts"
+}

package/component/dropdown-menu/package.json

@@ -0,0 +1,4 @@
+{
+  "module": "../../fesm2022/ojiepermana-angular-component-dropdown-menu.mjs",
+  "typings": "../../types/ojiepermana-angular-component-dropdown-menu.d.ts"
+}