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

@dsn-starter-kit/components-html

v3.5.0

Published

Pure HTML/CSS components for the design system

Readme

@dsn-starter-kit/components-html

Pure HTML/CSS components for the design system: no JavaScript required.

Use these components in static HTML pages, server-rendered templates, or any project that doesn't use a JavaScript framework.

Features

  • Pure CSS, no JavaScript dependencies
  • BEM class naming convention
  • Uses design tokens via CSS custom properties
  • Works with any templating language or static HTML

Installation

pnpm add @dsn-starter-kit/components-html

Usage

In HTML

Include the CSS and use BEM classes on standard HTML elements:

<link
  rel="stylesheet"
  href="@dsn-starter-kit/design-tokens/dist/css/variables.css"
/>
<link
  rel="stylesheet"
  href="@dsn-starter-kit/components-html/dist/components.css"
/>

<button class="dsn-button dsn-button--strong dsn-button--size-default">
  Save
</button>

<button class="dsn-button dsn-button--default dsn-button--size-small">
  Cancel
</button>

<button class="dsn-button dsn-button--strong-negative dsn-button--size-default">
  Delete
</button>

In JavaScript/TypeScript Projects

The package exports individual component CSS files:

// Import all components
import '@dsn-starter-kit/components-html';

// Or import individual components
import '@dsn-starter-kit/components-html/button';
import '@dsn-starter-kit/components-html/alert';
import '@dsn-starter-kit/components-html/modal-dialog';

Available exports:

  • ./action-group — Action group styles
  • ./alert — Alert component styles
  • ./backdrop — Backdrop overlay styles
  • ./body — Body component styles
  • ./breadcrumb-navigation — Breadcrumb navigation styles
  • ./breakout-section — Breakout section styles
  • ./button — Button component styles
  • ./button-link — ButtonLink component styles
  • ./card — Card component styles
  • ./checkbox — Checkbox styles
  • ./checkbox-group — Checkbox group styles
  • ./checkbox-option — Checkbox option styles
  • ./container — Container layout styles
  • ./date-input — Date input styles
  • ./date-input-group — Date input group styles
  • ./details — Details/summary styles
  • ./dot-badge — Dot badge styles
  • ./drawer — Drawer component styles
  • ./file — File component styles
  • ./file-input — File input styles
  • ./form-field — Form field styles
  • ./form-field-description — Form field description styles
  • ./form-field-error-message — Form field error message styles
  • ./form-field-label — Form field label styles
  • ./form-field-status — Form field status styles
  • ./form-fieldset — Form fieldset styles
  • ./grid — Grid layout styles
  • ./heading — Heading styles
  • ./heading-group — Heading group styles
  • ./hero — Hero section styles
  • ./icon — Icon component styles
  • ./image — Image component styles
  • ./link — Link component styles
  • ./link-button — LinkButton component styles
  • ./logo — Logo component styles
  • ./menu — Menu component styles
  • ./menu-button — Menu button styles
  • ./menu-link — Menu link styles
  • ./modal-dialog — Modal dialog styles
  • ./note — Note component styles
  • ./number-badge — Number badge styles
  • ./option-label — Option label styles
  • ./ordered-list — Ordered list styles
  • ./page-body — Page body styles
  • ./page-footer — Page footer styles
  • ./page-header — Page header styles
  • ./page-layout — Page layout styles
  • ./paragraph — Paragraph styles
  • ./popover — Popover component styles
  • ./pre-heading — Pre-heading styles
  • ./progress-bar — Progress bar styles
  • ./radio — Radio styles
  • ./radio-group — Radio group styles
  • ./radio-option — Radio option styles
  • ./search-input — Search input styles
  • ./select — Select component styles
  • ./skip-link — Skip link styles
  • ./spinner — Spinner component styles
  • ./stack — Stack layout styles
  • ./status-badge — Status badge styles
  • ./summary-list — Summary list styles
  • ./table — Table component styles
  • ./table-of-contents — Table of contents styles
  • ./text-area — Text area styles
  • ./text-input — Text input styles
  • ./time-input — Time input styles
  • ./unordered-list — Unordered list styles

Components that need another component's CSS

Some components put another component's classes in their own markup. The sort button in a Table column header carries dsn-button, a ButtonLink carries dsn-button, a LinkButton carries dsn-link. Import one of those on its own and you get the component's own rules without the ones it builds on, which renders as an unstyled button or link.

Each such component declares it at the top of its CSS:

/* packages/components-html/src/table/table.css */
/* @dsn-depends-on: button */

| Component | Also import | | ----------------- | ---------------------------- | | ./button-link | ./button | | ./date-input | ./text-input | | ./file | ./link, ./link-button | | ./heading-group | ./heading, ./pre-heading | | ./link-button | ./link | | ./menu-link | ./button | | ./search-input | ./text-input | | ./select | ./text-input | | ./table | ./button | | ./time-input | ./text-input |

Import the dependency first, so the component's own rules still win at equal specificity:

import '@dsn-starter-kit/components-html/button';
import '@dsn-starter-kit/components-html/table';

This does not apply to the . export: dist/components.css contains every component, ordered so that each one comes after what it depends on.

Available Components

| Component | CSS Classes | Export Path | | --------------------- | ---------------------------------------------------------------- | ---------------------------- | | ActionGroup | dsn-action-group | ./action-group | | Alert | dsn-alert, dsn-alert--{variant} | ./alert | | Backdrop | dsn-backdrop | ./backdrop | | Body | dsn-body | ./body | | BreadcrumbNavigation | dsn-breadcrumb-navigation | ./breadcrumb-navigation | | BreakoutSection | dsn-breakout-section | ./breakout-section | | Button | dsn-button, dsn-button--{variant}, dsn-button--size-{size} | ./button | | ButtonLink | dsn-button | ./button-link | | Card | dsn-card | ./card | | Checkbox | dsn-checkbox, dsn-checkbox__control | ./checkbox | | CheckboxGroup | dsn-checkbox-group | ./checkbox-group | | CheckboxOption | dsn-checkbox-option | ./checkbox-option | | Container | dsn-container | ./container | | DateInput | dsn-text-input, dsn-date-input | ./date-input | | DateInputGroup | dsn-date-input-group | ./date-input-group | | Details | dsn-details | ./details | | DotBadge | dsn-dot-badge, dsn-dot-badge--{variant} | ./dot-badge | | Drawer | dsn-drawer | ./drawer | | File | dsn-file | ./file | | FileInput | dsn-file-input | ./file-input | | FormField | dsn-form-field | ./form-field | | FormFieldDescription | dsn-form-field-description | ./form-field-description | | FormFieldErrorMessage | dsn-form-field-error-message | ./form-field-error-message | | FormFieldLabel | dsn-form-field-label | ./form-field-label | | FormFieldStatus | dsn-form-field-status, dsn-form-field-status--{variant} | ./form-field-status | | FormFieldset | fieldset.dsn-form-field | ./form-fieldset | | Grid | dsn-grid | ./grid | | Heading | dsn-heading, dsn-heading--heading-{level} | ./heading | | HeadingGroup | dsn-heading-group | ./heading-group | | Hero | dsn-hero | ./hero | | Icon | dsn-icon, dsn-icon--size-{size} | ./icon | | IconList | dsn-icon-list, dsn-icon-list__item, dsn-icon-list__icon | ./icon-list | | Image | dsn-image | ./image | | Link | dsn-link, dsn-link--external | ./link | | LinkButton | dsn-link | ./link-button | | Logo | dsn-logo | ./logo | | Menu | dsn-menu, dsn-menu--horizontal | ./menu | | MenuButton | dsn-menu-button | ./menu-button | | MenuLink | dsn-menu-link | ./menu-link | | ModalDialog | dsn-modal-dialog | ./modal-dialog | | Note | dsn-note, dsn-note--{variant} | ./note | | NumberBadge | dsn-number-badge | ./number-badge | | OptionLabel | dsn-option-label | ./option-label | | OrderedList | dsn-ordered-list | ./ordered-list | | PageBody | dsn-page-body | ./page-body | | PageFooter | dsn-page-footer | ./page-footer | | PageHeader | dsn-page-header | ./page-header | | PageLayout | dsn-page-layout | ./page-layout | | Paragraph | dsn-paragraph, dsn-paragraph--size-{size} | ./paragraph | | Popover | dsn-popover | ./popover | | PreHeading | dsn-pre-heading | ./pre-heading | | ProgressBar | dsn-progress-bar | ./progress-bar | | Radio | dsn-radio, dsn-radio__control | ./radio | | RadioGroup | dsn-radio-group | ./radio-group | | RadioOption | dsn-radio-option | ./radio-option | | SearchInput | dsn-text-input, dsn-search-input | ./search-input | | Select | dsn-text-input, dsn-select | ./select | | SkipLink | dsn-skip-link | ./skip-link | | Spinner | dsn-spinner | ./spinner | | Stack | dsn-stack, dsn-stack--space-{size} | ./stack | | StatusBadge | dsn-status-badge, dsn-status-badge--{variant} | ./status-badge | | SummaryList | dsn-summary-list | ./summary-list | | Table | dsn-table | ./table | | TableOfContents | dsn-table-of-contents, dsn-table-of-contents--plain | ./table-of-contents | | TextArea | dsn-text-area, dsn-text-area--size-{size} | ./text-area | | TextInput | dsn-text-input, dsn-text-input--size-{size} | ./text-input | | TimeInput | dsn-text-input, dsn-time-input | ./time-input | | UnorderedList | dsn-unordered-list | ./unordered-list |

Some components build on another component's block and need both stylesheets when you import export paths individually. ./select, ./search-input, ./date-input and ./time-input need ./text-input, and ./form-fieldset needs ./form-field. Importing dist/components.css gives you everything in the right order.

Component manifest

manifest.json is a machine-readable index of every component: its BEM block, category, purpose, which platform implementations exist, and its most important props. It needs no build step, so tooling and AI agents can read it directly.

import manifest from '@dsn-starter-kit/components-html/manifest';
import type {
  Category,
  ComponentEntry,
  Platform,
} from '@dsn-starter-kit/components-html/manifest';

const formControls: ComponentEntry[] = manifest.components.filter(
  (component) => component.category === 'form-input'
);

function componentsFor(platform: Platform): string[] {
  return manifest.components
    .filter((component) => component.platforms.includes(platform))
    .map((component) => component.name);
}

const categories: Category[] = ['form-input', 'form-option', 'form-field'];

The default export is typed as Manifest, so component.category and component.platforms are the narrow union types Category and Platform rather than plain string. The types live in manifest.d.ts and are exported from the same ./manifest path: Manifest, ComponentEntry, PropDefinition, Category and Platform. Both moduleResolution: "nodenext" and "bundler" resolve them.

manifest-schema.json describes the same structure as JSON Schema, for editors and for the validation step in the build. It is available as @dsn-starter-kit/components-html/manifest-schema if you want to validate your own additions against it.

Assets

SVG icons are available in assets/icons/ for use as inline SVGs:

assets/icons/
├── check.svg
├── chevron-down.svg
├── home.svg
├── ... (20 icons total)

Building

pnpm --filter @dsn-starter-kit/components-html build

The build validates manifest.json against manifest-schema.json before it concatenates any CSS, so an invalid category, an unknown platform or a misspelled field fails the build instead of shipping. Run that check on its own with:

pnpm --filter @dsn-starter-kit/components-html validate:manifest

The @dsn-depends-on comments determine the order in dist/components.css: a component is emitted after everything it declares. Use a comment rather than an @import here. An @import would survive into the bundled CSS with a relative path that resolves to nothing from dist/, and the bundler of a consuming package would inline the same file a second time, after the overriding rules.

License

MIT