Install Angular UI Libraries with ng add | ng-hub-ui

Interactive examples

Explore live examples that show how the library behaves in common Angular use cases.

One Command

`ng add ng-hub-ui` is the whole installation. The Angular CLI fetches the package, runs its `ng-add` schematic, and the schematic asks which of the 25 catalogued libraries you want. Space selects, `a` toggles everything, `i` inverts the selection; confirming resolves the choice into npm packages, writes them into `dependencies` and hands the install to whichever package manager the CLI detected.

Flags And Scripts

The prompt is skippable, which is what makes the installer usable from CI and from a project's own setup script. `--libraries` accepts a comma-separated list or the same flag repeated, and both forms normalize identically: trimmed, de-duplicated, in the order they were given. `--skip-install` writes the manifest and stops there. Pass the identifiers from the catalogue, not the labels the prompt renders — they are different strings, and an unknown one stops the schematic before `package.json` is touched.

Resolved Dependencies

A selection is not the list of packages that gets written. Each catalogued library names the peers it needs — `ng-hub-ui-utils` for most of the family, `ng-hub-ui-ds` for panels, `ng-hub-ui-forms` for signature, and `sortablejs`, which is not ours at all — and resolution is transitive, so a co-installed library contributes its own peers in turn. Every range floors at or above the highest peer the family declares on it, which is what keeps the write from producing a pair npm cannot satisfy. A key already present is never rewritten, so a version you have pinned survives. The schematic stops at dependency wiring: no `angular.json`, no providers, no component registrations, no stylesheet entries.