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

ngwind

v0.1.0

Published

A headless-first Angular UI component library built on @angular/cdk and @angular/aria, styled with Tailwind CSS.

Downloads

130

Readme

ngwind

A small Angular component library built on @angular/cdk and @angular/aria, styled with Tailwind CSS v4 utility classes.

| Component | Built on | Selector(s) | | --------- | ------------------------- | --------------------------------------------------------------- | | Button | native element | button[tw-button], a[tw-button] | | Card | content projection | tw-card (+ [tw-card-header], [tw-card-footer]) | | Dialog | @angular/cdk/dialog | TwDialog service (+ title/content/actions directives) | | Tooltip | @angular/cdk/overlay | [twTooltip] | | Tabs | @angular/aria/tabs | tw-tabs, tw-tab-list, button[tw-tab], [tw-tab-panel] | | Accordion | @angular/aria/accordion | tw-accordion, tw-accordion-item (+ [tw-accordion-header]) |

Installation

ng add ngwind

That's it. ng add ngwind installs the @angular/cdk and @angular/aria peer dependencies and configures your global stylesheet automatically (see Required setup for what it wires up). Requires Tailwind CSS v4 to already be set up in your app.

pnpm add ngwind @angular/cdk @angular/aria

Then apply the Required setup below by hand.

Required setup

The library ships raw Tailwind utility classes in its templates rather than compiled CSS. Those classes only become real CSS when your app's Tailwind build scans the library, and the CDK overlays need structural CSS. ng add ngwind adds both lines for you; if you installed manually, add them to your global stylesheet (e.g. src/styles.css):

@import 'tailwindcss';

/* 1. Let Tailwind scan this library so its utility classes are emitted. */
@source '../node_modules/ngwind/**/*.mjs';

/* 2. Structural CSS for CDK overlays (Dialog + Tooltip positioning & backdrop). */
@import '@angular/cdk/overlay-prebuilt.css';

Without (1) buttons/cards/etc. render unstyled. Without (2) the Dialog and Tooltip overlays appear mispositioned with no backdrop.

In this repo's demo app the @source points at the library source (../../ui/src/**/*.{html,ts}) because it consumes the library from dist/ within the same workspace. An external consumer points it at node_modules/ngwind instead.

Usage

Button

<button tw-button variant="primary" size="md">Save</button>
<button tw-button variant="destructive" [disabled]="true">Delete</button>
<a tw-button variant="outline" href="/docs">Docs</a>

Variants: primary | secondary | outline | ghost | destructive. Sizes: sm | md | lg.

Card + Tooltip

<tw-card>
  <h3 tw-card-header>Title</h3>
  <p>Body content.</p>
  <div tw-card-footer>
    <button tw-button twTooltip="Saves your changes" tooltipPosition="above">Save</button>
  </div>
</tw-card>

Tooltip positions: above | below | left | right.

Dialog

import { TwDialog } from 'ngwind';

private readonly dialog = inject(TwDialog);

open() {
  const ref = this.dialog.open<boolean>(ConfirmDialog, { data: { /* ... */ } });
  ref.closed.subscribe((result) => { /* ... */ });
}

Inside the dialog component use [tw-dialog-title], [tw-dialog-content], and [tw-dialog-actions], and inject DialogRef / DIALOG_DATA (re-exported from ngwind).

Tabs

<tw-tabs>
  <tw-tab-list [(selectedTab)]="active">
    <button tw-tab value="a">Tab A</button>
    <button tw-tab value="b">Tab B</button>
  </tw-tab-list>
  <div tw-tab-panel value="a">Panel A</div>
  <div tw-tab-panel value="b">Panel B</div>
</tw-tabs>

Accordion

<tw-accordion [multiExpandable]="false">
  <tw-accordion-item>
    <span tw-accordion-header>Section title</span>
    <p>Section content.</p>
  </tw-accordion-item>
</tw-accordion>

Building

pnpm ng build ui      # build the library -> dist/ui
pnpm start            # run the demo showcase app