@warmio/ui
v1.5.2
Published
Portable, sealed React components for Warm products.
Downloads
539
Readme
@warmio/ui
Portable React components shared by Warm products. The next package version is @warmio/[email protected]
with the exact @warmio/[email protected] CSS/primitive contract. Import @warmio/design/globals.css once, and add
the package's compiled files to Tailwind's source detection:
Why these files are separate
Independently deployed Warm products cannot import runtime code from the private warm-app
workspace, so libraries/public-ui/ must be a standalone public package rather than another private
workspace entry point. tools/tasks/check-ui-package.mjs is a dedicated package-boundary check
because the existing application checks do not build, pack, and inspect a public npm tarball.
.github/workflows/publish-ui.yml is separate from application deployment workflows so npm trusted
publishing can bind credentials to one reviewable package-release boundary without granting an app
deployment permission to publish packages.
@import '@warmio/design/globals.css';
@source '../node_modules/@warmio/ui/dist';The 1.5.2 public UI surface keeps the Warm badge, Text and StackedDisplay, DropdownMenu,
Sheet, the complete responsive Sidebar family, and the ProductHeader composition. Button,
ButtonLink, Logo, and WarmLogoIcon are directly owned by @warmio/[email protected] and are
re-exported through UI where applicable. ProductHeader owns the responsive frame,
breadcrumb/title semantics, leading slot, action slot, and optional portal targets used by Warm
product shells. Styling is sealed: use documented semantic properties and layout wrappers, never
className or style overrides. DropdownMenu interaction feedback requires the exact public peer
[email protected]. Fluid-derived menu, sidebar, and sheet interactions require motion@^12.42.2.
The closed props and Warm styling remain unchanged. Motion respects live reduced-motion
preferences. Adapted Fluid source is covered by LICENSES/fluid-functionalism.txt.
These versions require publication before independently deployed consumers can install them.
The published artifact is standalone and never imports private warm-app workspace packages.
