trineui

trineui is the public Trine package. It ships:

• the CLI used by npx trineui@latest ...
• runtime helper subpath exports used by generated local component source
• the source-owned Angular consumer contract based on trine.json
• the contract that hides registry infrastructure behind init, add, diff, and upgrade

Quickstart

From an Angular app root:

npx trineui@latest init
npx trineui@latest add button
npx trineui@latest add combobox
npx trineui@latest diff button
npx trineui@latest upgrade button

init creates:

• src/styles/tokens.css
• src/styles/base.css
• postcss.config.json
• trine.json

It also patches the Angular app stylesheet entry to import Tailwind v4 and the generated token/base styles, and it ensures the consumer app depends on trineui.

add button copies these consumer-owned files into the target app:

• src/app/ui/button/button.ts
• src/app/ui/button/button.html
• src/app/ui/button/button.skin.css
• src/app/ui/button/button.types.ts

add combobox copies these consumer-owned files into the target app:

• src/app/ui/combobox/combobox.ts
• src/app/ui/combobox/combobox.html
• src/app/ui/combobox/combobox.skin.css
• src/app/ui/combobox/combobox.types.ts

The app owns those files after delivery. Trine does not keep runtime ownership of delivered component source.

Current scope

What works right now:

• Angular-first init
• CDN/static-registry-backed add button
• CDN/static-registry-backed add combobox
• diff
• upgrade
• source-owned component delivery
• URL-served registry payloads with trineuiRange compatibility checks
• runtime helper subpath exports:
  • trineui/a11y
  • trineui/interactions
  • trineui/forms
  • trineui/overlay
  • trineui/platform
  • trineui/utils
  • trineui/tokens

The component registry is not another user-facing package. It is a set of static assets served behind the registry URL recorded in trine.json. The default registry now points at https://trineui-registry.pages.dev, which is served independently from the npm package. Component updates can be deployed to the registry without requiring a new trineui npm release.

What is intentionally out of scope right now:

• broad multi-component guarantees
• non-Angular consumer support
• Storybook / Chromatic

Package preparation

Before packing or publishing from this repo:

pnpm --filter trineui run prepare:package

That command rebuilds dist/ and validates the CLI runtime against the current TypeScript source.

Release note

This package can be prepared and dry-run validated from this repo. Public release now follows: registry build/validate -> registry deploy -> npm publish -> smoke-proof.