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

ng-comps

v4.0.2

Published

Angular UI components for mf-design-system

Readme

ng-comps

Angular UI library built on top of Angular Material with a public accessibility contract.

Installation

npm i ng-comps

Import only what you use:

import { MfButtonComponent } from 'ng-comps';

Load the shared tokens and base styles in your global stylesheet:

@import 'ng-comps/theme/tokens.css';
@import 'ng-comps/styles.css';

Accessibility Contract

ng-comps v1 is designed to support:

  • WCAG 2.2 AA implementation targets in the component layer
  • EN 301 549 evidence mapping when the library is used as documented
  • Contractual reporting against EN 301 549 v3.2.1 / WCAG 2.1 AA until the next EN update is formally published

The library is accessible by default only when consumers keep the semantic contract intact:

  • interactive components must have an accessible name
  • visible labels are preferred over placeholders
  • overlays must be opened through the provided accessible APIs
  • row actions in tables must be explicit and focusable
  • custom theming must preserve contrast and visible focus states

Read the full contract, QA matrix, limitations, and VPAT-oriented notes in ACCESSIBILITY.md.

Development

npm run build:lib
npm run test:ci
npm run build-storybook
npm run ci

npm run ci executes the local gate used by CI:

  • library build
  • unit and accessibility tests
  • Storybook static build

Storybook

Storybook is the primary documentation surface for component usage and accessibility contracts.

  • component API stories live in src/stories
  • accessibility contract stories cover keyboard, focus, overlays, and explicit actions
  • anti-patterns are documented as examples of what not to ship

Publishing

This repository publishes from dist/ng-comps, not from the workspace root.

npm run build:lib
npm run prepare:package
npm run release:dry-run
npm run publish:npm

Important Limitation

Using ng-comps does not make an application automatically conformant with WCAG or EN 301 549. Final conformance still depends on product copy, content, workflows, application state management, custom wrappers, and consumer integration decisions.