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

bismuth-ui

v0.8.6

Published

Vue 3 components cut from hexagons: 45° bevels drawn in CSS layers, an iridescent contour, and a theme that swaps with one custom property.

Readme

bismuth-ui

Vue 3 components cut from hexagons. The bevel is always 45°, the contour is a stack of CSS layers rather than a border, and the whole palette moves on one custom property.

npm i bismuth-ui
import { BButton, BSelect } from 'bismuth-ui';
import 'bismuth-ui/style.css';

Peers: vue ≥ 3.5, @vueuse/core, motion-v — and nothing else. Icons are drawn inline; the library brings no icon set of its own.

Theming

Components never reach for a palette colour. They read semantic tokens, so a theme is a handful of custom properties — no rebuild, no config file.

:root {
  --b-surface: #f6f5fa; /* the page */
  --b-elevated: #ffffff; /* the plate a control is cut from */
  --b-line: #d7d4e3; /* contours at rest */
  --b-line-strong: #a9a5bd; /* and under the pointer */
  --b-text: #17161f; /* writing, and what a control falls back to */
}

--b-tone is the colour a control says things with — fills, focus, the mark on a chosen row. It is deliberately not declared: left alone, every control takes the page's own ink, and setting it anywhere overrides that from there down. So it colours a whole form as readily as one control:

<div style="--b-tone: #00b073">
  <BSlider v-model="volume" />
  <BSwitch v-model="notify" />
</div>

Light and dark are the same tokens declared twice — [data-theme='light'] and a prefers-color-scheme fallback. BThemeToggle flips the attribute.

The iridescent ring has its own: --b-spectrum for the colours, --b-speed-slow | -normal | -fast for how fast it travels.

Sizes

Every component takes size: xs | sm | md | lg | xl. Sizes are classes, not inline styles, so a stylesheet can still override them. There are no pixel props — the geometry is the library's, and only the size and the colour are yours.

Components

| | | | --- | --- | | BButton | spectrum, plain, outline (glass), ghost | | BInput BTextarea BField BFieldAddon | the field shell and its slots | | BSelect BAutocomplete | grow with their values; a list underneath | | BDropdown BOption BOptionGroup | a panel on a trigger, and rows for it | | BSlider | ticks, range, a bubble over the handle | | BSwitch BProgress BLoader | | | BScrollArea | bars of its own; gutter="stable" keeps their room either way | | BResizable | pulled to size by a grip that keeps out of a scroll bar's way | | BDialog | a window over the page, mounted only while open; the panel inside is yours | | BTabs BTabList BTab BTabPanels BTabPanel | assembled by you; only the chosen panel is mounted, and it slides in from the side it sits on | | BPagination | pages as rhombi; a slot puts figures or anything else in them | | BDivider | a rule with a rhombus set into it | | BFrame BThumb | the shape and the handle, for building your own |

Also exported: vRipple (the press wave), cn (class merge), useDismiss, useListCursor, useFieldControl, and the cva variant builders behind each component.

Composing

Nothing is closed. BDropdown has one slot and imposes no layout — scrolling is opt-in, and the regions inside are laid out by whoever uses it. A select that should read “3 chosen” instead of listing chips is the value slot:

<BSelect v-model="picked" multiple :options="options">
  <template #value="{ option }">
    <span v-if="option.value === picked[0]">Chosen: {{ picked.length }}</span>
  </template>
</BSelect>

Development

npm run dev        # the demo stand
npm run build      # the stand, to dist-demo
npm run build:lib  # the package, to dist