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

@thunderbirdops/services-ui

v1.5.1

Published

A UI component library for use with Thunderbird Services

Readme

Services UI

A UI component library for use with Thunderbird Services

Note this is heavily work-in-progress.

Usage

Install the library:

npm i @thunderbirdops/services-ui

Include the stylesheet into your top-level component:

import '@thunderbirdops/services-ui/style.css';

Now you can use UI components by importing them in your components:

import { PrimaryButton } from '@thunderbirdops/services-ui';

Library Development

We have the following structure for Vue components:

  1. src/foundation/: Foundational items (typography, icons, spacing, etc.)
  2. src/components/: Design system components (buttons, badges, etc.)
  3. src/patterns/: Custom usage or bundling of two or more design system components (copy button, standard footer, etc.)

Storybook

You can access storybook by running:

npm run storybook

Building

You can build the library by running:

npm run build

Publishing a new version

Once a release is deemed either a major update, minor update or patch update go ahead and update the version in package.json. Don't forget to run npm i to update the package version number in the lockfile too.

Once that's done commit it with the version number (i.e. if the new version is 0.6.1, commit just package.json and package-lock.json with the message "0.6.1".)

After that create a tag for that commit as v$versionNumber (i.e. v0.6.1 from our previous example.) and draft and publish a new release based off that tag. The npm automation should kick in, and it should publish that new version soon.

Exporting as Web Components

Using Vite, you can create Web Components (also known as "Custom Elements") from Vue components.

Running npm run build:ce ("ce" for "Custom Elements") produces two files that can be included in a static website:

  • dist/boltweb.iife.js
  • dist/boltweb.css

Example usage:

<bolt-primary-button variant="outline" href="{{ url('roadmaps.desktop') }}">
  Visit Desktop Roadmap
</bolt-primary-button>

Specifying which components to export

In /src/index.ce.ts, there are 4 steps for specifying the Vue components that will be exported as Web Components:

  1. Import the components.
  2. Call defineCustomElement.
  3. Register a tag name.
  4. Add the converted element to the export object.

For reference, here's the code that performs those steps for PrimaryButton:

// Import the Components to convert.
import { PrimaryButton } from './main';

// Convert each to a Web Component.
const BoltPrimaryButton = defineCustomElement(PrimaryButton);

// Register globally.
customElements.define('bolt-primary-button', BoltPrimaryButton);

// Provide components for use.
export { BoltPrimaryButton };

Displaying the text content of a Web Component

When you use one of the Web Components in your markup, you will likely want to specify the text content:

<bolt-primary-button variant="outline" href="{{ url('roadmaps.desktop') }}">
  Visit Desktop Roadmap
</bolt-primary-button>

In this example, "Visit Desktop Roadmap" is rendered via the default slot of the Vue component.

If the component you want to use does not have a default slot, add it:

 <template>
   <base-button type="primary">
     <template v-for="(_, name) in $slots" v-slot:[name]="slotData">
       <slot :name="name" v-bind="slotData" />
     </template>
+    <slot />
   </base-button>
 </template>

If you do not want to modify the component, you can also use named slots (which requires wrapping your text in an additional HTML element). See [[https://vuejs.org/guide/extras/web-components.html#slots][the Vue docs]] for more information.