Allow installing components using a specific version (deterministic installs)

[maciej-winware]

Problem or use case

Currently the CLI version can be pinned, for example:

npx untitledui@0.1.55 add button

However, the CLI fetches components from the Untitled without specifying any component version. As a result, the installed component code may change over time even when using the same CLI version.

Additionally, there does not appear to be any publicly accessible versioning for the React components themselves (e.g., tags, releases, or versioned component snapshots). This makes it impossible to install or reference a specific component version.

For teams integrating Untitled UI components into production codebases, this creates several risks:

• installs are not deterministic
• the same command may generate different code over time
• debugging regressions becomes harder
• rollbacks to a known-good component state are difficult
• CI or reproducible builds cannot guarantee identical outputs

Installing components should be deterministic so that the same command always produces the same component code.

Proposed solution

Allow installing components using a specific version. For example:

npx untitledui@0.1.55 add button@0.1.55

or

npx untitledui@0.1.55 add button --components-version 0.1.55

This could be implemented by:

• adding a version parameter to the components API
• maintaining immutable versioned component snapshots
• mapping CLI versions to specific component catalog versions

Ideal solution - publish versioned react components as an npm package (@untitledui/react). Using npm for component distribution simplifies versioning and reproducibility.

The key requirement is that component installs should be reproducible for a given version.

Alternatives considered

No response

Examples or mockups

No response

[deebov]

Hey @maciej-winware, thanks for the suggestion. I'll add this to out backlog.