npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@daihum/ui-core

v0.1.8

Published

Platform-independent DAIHUM UI contracts, state models, and pure helpers.

Readme

@daihum/ui-core

Platform-independent DAIHUM UI contracts, state models, and pure helpers.

This package is the non-DOM substrate below the web implementation in @daihum/ui. It must not depend on React, React DOM, Radix, shadcn runtime components, Tailwind CSS, browser APIs, or product runtime policy.

Internal substrate — not a consumer-facing API. External product consumers (Carrel, Ontal, and their @carrel/ui-web / @ontal/ui facades) must not import @daihum/ui-core directly. Every capability they need is re-exported through a @daihum/ui/* subpath (e.g. @daihum/ui/dock-layout, @daihum/ui/data-table-vnext/contracts). Only @daihum/ui itself and other daihum-internal non-React packages (workers, AI catalog/projection code) depend on @daihum/ui-core. This keeps a single consumer surface — @daihum/ui — while the React-free logic lives here as an implementation detail.

The contract/logic modules currently living here (all re-exported through @daihum/ui/*):

| core module | consumer-facing re-export | |---|---| | model-picker (+ /contracts /builders /formatters) | @daihum/ui/model-picker (+ subpaths) | | data-table-vnext (+ /contracts /backend) | @daihum/ui/data-table-vnext (+ subpaths) | | action-menu | @daihum/ui/action-menu | | desktop-canvas | @daihum/ui/desktop-canvas | | dock-layout | @daihum/ui/dock-layout | | panel-region | @daihum/ui/panel-region | | settings-registry | @daihum/ui/settings-registry | | surface-registry | @daihum/ui/surface-registry | | work-area | @daihum/ui/work-area | | workspace-file | @daihum/ui/workspace-file |

Each @daihum/ui/<name> subpath is a thin re-export of the matching core module, so consumers get the React-free contracts/state/helpers without ever naming @daihum/ui-core. The web composed surfaces (@daihum/ui/data-table-vnext React table, @daihum/ui/shell, the forthcoming workbench/panel surfaces) build on these same contracts; browser worker setup and React rendering stay in the web package.

Keep this package free of rendered controls, provider catalog authority, gateway policy, settings persistence, and product copy — those belong in @daihum/ui, the DAIHUM AI packages, or downstream products. This package holds only the platform-independent contracts, state models, and pure helpers that the web layer and internal non-DOM code share.

Proofs

Run these from the DAIHUM repo root after changing core contracts or helpers:

  • pnpm --filter @daihum/ui-core typecheck
  • pnpm --filter @daihum/ui-core build
  • pnpm --filter @daihum/ui-core test
  • npm run proof:ui-boundaries
  • npm run proof:ui-downstream-imports

proof:ui-boundaries includes a temporary no-DOM consumer for the model-picker core helpers. The downstream proof compiles temporary Carrel and Ontal consumers that import every capability through @daihum/ui/* (model-picker, data-table-vnext, and the headless dock-layout / panel-region / work-area / desktop-canvas / settings-registry / surface-registry / workspace-file / action-menu re-exports), and it git greps the real consumer repos to assert zero direct @daihum/ui-core imports (the no-core-leak boundary guard).