Install Angular UI Libraries with ng add | ng-hub-ui
The ng-hub-ui family installer: one ng add command that asks which libraries you want, resolves the packages each of them needs and writes them into your manifest.
Last updated Sep 8, 2026
Overview
Why teams search for this library
Use ng-hub-ui when you are adding one or more of the family's libraries to an Angular workspace and would rather not work out by hand which peer package each of them needs.
Install
ng add ng-hub-uiJump to
Ideal for
- Adding several ng-hub-ui libraries to an Angular workspace in one step
- Scripting a project's initial setup in CI without answering a prompt
- Letting the peer packages each library needs be worked out for you
About ui
ng-hub-ui is the umbrella package of the family, and the only published one that ships no components. What it ships is an ng-add schematic. It offers the 25 catalogued libraries in a multi-select prompt, or takes their identifiers straight from a --libraries flag, and resolves the selection into the npm packages it actually needs — including the peers a library depends on and the one external package, sortablejs, that is not ours. The resolved list is written into dependencies at the workspace root, never overwriting a key that is already there, and then handed to whichever package manager the Angular CLI detected. Its scope stops at dependency wiring: it does not touch angular.json, register providers, import components or add stylesheet entries.
Feature guides
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.
Examples:
Interactive install
The command and the prompt it opens, as they appear in the terminal.
Space selects, a toggles everything and i inverts the selection. The schematic writes the chosen packages into dependencies and then lets the package manager install them.
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.
Examples:
Flags instead of the prompt
The three non-interactive forms, and the two ways a bad selection is refused.
Comma-separated
Repeated flag — the same selection, normalized the same way
Manifest only, install left to you
An empty selection fails with Select at least one ng-hub-ui library to install. and an unknown identifier with Unknown ng-hub-ui library: <id>. — in both cases 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.
Examples:
What the selection writes
Two libraries asked for, five packages written — the co-installs made concrete.
Two libraries asked for…
…five packages written into package.json
The schematic adds a dependency only when the key is absent, so a version already pinned in your manifest survives the install untouched.
Key features
Recent changes
Version 0.2.1 - 9/8/26, 12:00 AM
fixed: Four documents said the installer has no page on the documentation site. This is that page: both READMEs and `FUNCTIONALITIES.md` link to it instead of denying it.
changed: The manifest `homepage` points at this page rather than at the family root — it is the link a registry shows beside the package, and every other library in the family already points at its own documentation. Metadata only: no code, no schematic behaviour, no catalogue change.
Version 0.2.0 - 9/6/26, 12:00 AM
fixed: Every one of the 25 catalogue ranges now floors at or above the highest peer the family declares on it. `ng-hub-ui-forms` had reached 22.32.0 peering on `ng-hub-ui-utils >=22.12.0` while the catalogue still offered `utils ^22.8.1`, so `ng add ng-hub-ui --libraries=forms` wrote a pair npm cannot satisfy — invisible on a fresh unpinned install, an `ERESOLVE` anywhere resolution was already fixed.
fixed: Both READMEs denied a library the installer has offered since 0.1.6: they said `ng-hub-ui-action-sheet` was not on npm, in five separate places, while the catalogue had carried it all along.
changed: The Angular peer range is `>=18.0.0`, up from `>=17.3.0`. Nothing in the catalogue targets Angular 17, so the old floor let `ng add ng-hub-ui` run, write the manifest and only then fail to resolve. See `BREAKING_CHANGES.md`.
added: The schematic has a tracked spec again. The only test over `ng add` lived beside the compiled output where `.gitignore` excludes it, so it left the repository the moment it was written; run today it reported three failures it had been reporting for months.
Version 0.1.7 - 9/1/26, 12:00 AM
changed: The manifest `homepage` points at the localized site root rather than the redirect above it, so a reader arriving from npm lands one hop earlier.
Version 0.1.6 - 8/30/26, 12:00 AM
added: `action-sheet` joins the catalogue and the prompt: `ng-hub-ui-action-sheet` reached the registry with 22.0.0, and it needs no co-installs.
Related libraries
Frequently asked questions
How do I install ng-hub-ui in an Angular project?
Run ng add ng-hub-ui. The Angular CLI fetches the installer package and runs its ng-add schematic, which asks which of the 25 catalogued libraries you want, writes the resolved packages into dependencies and lets your package manager install them.
Can I install ng-hub-ui libraries without the interactive prompt?
Yes. Pass the identifiers to --libraries, either comma-separated (--libraries=modal,paginable) or as a repeated flag (--libraries=modal --libraries=paginable). Add --skip-install to update package.json and leave the install to you.
What does the ng-hub-ui schematic change in my project?
Only the dependencies block of the workspace root package.json, and only keys that are not already there. It does not touch angular.json, register providers, import components or add stylesheet entries.