Behive Tech Component Registry

Button

v0.5.0Stable

A flexible button component with variants, sizes, loading and disabled states.

pnpm add @behivetech/atoms.button

Published to npm.pkg.github.com

Checking the registry…

Changelog

v0.5.0

Minor Changes

  • b356876: Button's ghost label colour is now read from the --button-label-color custom property, defaulting to primary so an existing ghost button renders as before. A raised surface sets it on its own class when primary is under 4.5:1 (4.02:1 on the-behive's Dark surface-container-high; the default tokens give 8.43:1). ConfirmDialog sets it to secondary for Cancel: 12.87:1 in Dark and 5.40:1 in Light with the-behive's tokens. Inside a Modal or Drawer, set the property through their className or on a class inside the body, because their content portals to body.

Patch Changes

  • 408d5a9: The outlined secondary variant's label now reads --button-label-color as well as ghost, defaulting to primary so an existing outlined button renders as before. A raised surface that sets the property fixes both variants; primary and danger ignore it. With the-behive's tokens primary is 4.02:1 on Dark surface-container-high, secondary 12.87:1 (Dark) and 5.40:1 (Light).

v0.4.4

Patch Changes

  • 0c52e51: Each published package now says what it is and where its docs are: description from the README's first paragraph, and homepage plus a Docs: line in the README pointing at the package's page on https://bht-galaxy.vercel.app, all applied at publish time from one source. Seven READMEs that still said "TODO" have a summary; @behivetech/atoms.stat and @behivetech/cms.base-styles have a README at all; the hand-written props tables are gone from the READMEs, since the Props tab on the site is generated from the interface.

v0.4.3

Patch Changes

  • c733fc5: Published to the public npm registry (registry.npmjs.org, access public, with provenance) instead of GitHub Packages. Install with no registry configuration: pnpm add @behivetech/atoms.button. The versions already on GitHub Packages stay there; nothing in the packages changed.

v0.4.2

Patch Changes

  • e3bf015: Live examples are <name>.example.tsx (was <name>.composition.tsx), following template 0.4.0 of the component registry: the published files list and the docs site's Examples tab use the new name. No component code changed.

v0.4.1

Patch Changes

  • 726a7ab: The component registry is now the bht-component-registry template, adopted into this repo: every package lives at registry/behivetech/<category>/<name> and builds with the template's shared env. Published output is the same code; the class-name helper is bundled into each package instead of being a runtime dependency on @behivetech/get-class-name, the tarball now ships README.md, the source, the compositions and a docs.json the docs site reads, and each package declares license: MIT.

v0.4.0

Minor Changes

  • a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from --md-sys-* tokens, and each one falls back to the pre-MD3 --color-* name. Hardcoded brand colors and filter: brightness() are gone, so components follow the theme in both light and dark.

    Interaction

    • Hover, focus and press show a translucent layer of the content color.
    • Interactive controls get a :focus-visible ring.
    • Small controls get a 48px touch target without changing their drawn size.

    Props and component sizes are unchanged.

    Visible changes

    • Buttons are pill-shaped.
    • Text fields are outlined with a transparent fill.
    • FormField labels use body-small type.
    • Tooltips and toasts use the inverse surface.
    • Modal has no outline and 28px corners.
    • The hero headline is display-medium at regular weight.
    • Sidebar and NavItem no longer read cms-admin's --admin-sidebar-* variables.

    Fixes: these never matched and now work:

    • The NavItem active state.
    • Spinner sizes.
    • Button icon-only widths.
    • Table row dividers.

    Specificity: modifier styles now use .BHT__X--mod.BHT__X (0-2-0). A single-class className override of a modifier-controlled property needs matching specificity to win.

v0.3.1

Patch Changes

  • f8c57db: Generate TypeScript declarations once per build instead of once per format.

    dist/index.d.cts is no longer emitted. Nothing referenced it: each package's exports["."].types points at dist/index.d.ts, which is unchanged and still covers both the import and require conditions. There are no API, type, or runtime changes.

v0.3.0

Minor Changes

  • 08d7dd6: class names are namespaced with a BHT__ prefix, and sizing moves to rem

v0.2.1

Patch Changes

  • 86c5d3b: feature/54-page-list-and-new-page-form

v0.2.0

Minor Changes

  • 210f9a4: 36: Move editor, registry, and renderer into cms-admin

Patch Changes

  • cbe4e02: 36: MCP server, agents and other various fix
  • Updated dependencies [cbe4e02]
    • @behivetech/get-class-name@0.0.6

v0.1.0

Minor Changes

  • 4f8f5a7: Adding cms admin dashboard

v0.0.7

Patch Changes

  • 58c6730: Fixes for package styling not getting included

v0.0.6

Patch Changes

  • 0a62691: Updated all styling and added base vars for cms and components

v0.0.5

Patch Changes

  • 23ecde9: Fixes for CI issues and build issue with atro
  • Updated dependencies [23ecde9]
    • @behivetech/get-class-name@0.0.5

v0.0.4

Patch Changes

  • 2c5f4bd: Fix import export issues on packages
  • Updated dependencies [2c5f4bd]
    • @behivetech/get-class-name@0.0.4

v0.0.3

Patch Changes

  • 704ad1d: Updates to all versioning on the packages to all local packages
  • Updated dependencies [704ad1d]
    • @behivetech/get-class-name@0.0.3

v0.0.2

Patch Changes

  • 5e2a114: Initial push of all packages
  • Updated dependencies [5e2a114]
    • @behivetech/get-class-name@0.0.2