CLI & registry
Components are distributed as code you own, not a NuGet dependency. The navius CLI copies a component's source, plus everything it depends on, into your project.
Install the tool
dotnet tool install -g navius --prerelease
List what's available
navius list
Add a component
Resolves the component's registryDependencies (e.g. core, cn), copies the files in, and rewrites the namespace to yours.
navius add dialog --to ./src/MyApp --namespace MyApp.Ui
Some items also declare NuGet dependencies; the CLI prints the dotnet add package lines to run. The cn helper pulls in TailwindMerge.NET, which resolves Tailwind class conflicts so a consumer class beats a component's base classes.
Styled-only
Want to own the styled layer but keep the headless brain as a package? --styled-only copies just the styled Zits* and lib files and skips the brain, which you then reference as the Navius.Primitives NuGet package. The command prints the wiring to finish (the package reference, AddNavius(), and the interop asset that loads itself from the package). It cannot be combined with --namespace.
navius add date-picker --styled-only --to ./src/MyApp
Overwriting files
Because the copied code is yours to edit, add skips any target file that already exists rather than clobbering your changes. Pass --overwrite to force a fresh copy.
navius add dialog --overwrite
The registry
The registry is plain JSON modelled on a registry-item schema, so anyone can host their own. Each item lists its files and dependencies; the CLI reads it to resolve a copy.
{
"name": "dialog",
"registryDependencies": ["core", "cn"],
"files": ["Components/Dialog/ZitsDialog.razor", "..."]
}