Coming from PrimeNG
What maps across, and what deliberately does not.
PrimeNG is a good library and this is not a drop-in replacement for it. If you are migrating piece by piece, here is the honest mapping.
| PrimeNG | Here | Difference that matters |
|---|---|---|
| p-inputSwitch | hk-switch | Signal model, three sizes, no ripple |
| p-tabView | hk-tabs | Indicator measures real boxes; panels are separate elements |
| p-toast + MessageService | hk-toast-host + HkToastService | Typed payload, stack cap, pause on focus |
| p-accordion | hk-accordion | Animates grid rows, so unknown heights still ease |
| p-table | hk-table | Smaller and virtual-scroll first; fewer built-in features |
| PrimeNG theme presets | CSS custom properties | No preset objects — read and edit the tokens directly |
Running both at once
They do not collide: selectors are prefixed hk-, and the token layer only defines --hk-* properties. Migrate one screen at a time.
What you lose: PrimeNG has far more surface area — charts, org charts, editors, a much richer table. Nothing here pretends to replace those yet.