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

@jablonowski/dsb-components

v1.0.6

Published

Design System Blueprint - Angular UI Components

Readme

@jablonowski/dsb-components

Angular 19 standalone components built on @jablonowski/dsb-tokens.

Install

npm install @jablonowski/dsb-components @jablonowski/dsb-tokens

The token package is a peer dependency, not a bundled one — you and this library must resolve the same copy, because the custom properties these components read are the ones your stylesheet defines.

Import the stylesheet — this is not optional

/* your global stylesheet */
@import '@jablonowski/dsb-tokens/css';

Or in angular.json:

"styles": [
  "node_modules/@jablonowski/dsb-tokens/dist/css/public.css",
  "src/styles.css"
]

Every component in this library styles itself through var(--ds-decisions-*) and var(--ds-component-*) — 261 custom properties in total. Without the stylesheet, each of those declarations is dropped by the browser, and the components render with no padding, no control heights and inherited colours. They look broken rather than unstyled, and nothing reports an error: an undefined custom property is not a failure in CSS, it is a declaration the browser quietly discards.

Use

import { ButtonComponent, InputComponent } from '@jablonowski/dsb-components';

@Component({
  standalone: true,
  imports: [ButtonComponent, InputComponent],
  template: `<dsb-button variant="primary">Save changes</dsb-button>`,
})
export class MyComponent {}

Full component list, inputs, outputs and usage guidance for coding agents: llms.client.txt, shipped inside this package.

Theming

Do not override --ds-component-*. Those are internals of components you did not write, and the component owner is free to repoint them.

Override the decisions layer instead:

:root {
  --ds-decisions-color-action-primary-background: #0b5fff;
  --ds-decisions-space-md: 12px;
}

One decision reaches every component that expresses that intent, which is the entire reason the layer exists.

Versions

This library declares the oldest token release that carries every variable it references. Installing an older one is the failure described above, and npm will warn you about the unmet peer rather than let it happen quietly.