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

@tedi-design-system/angular

v6.2.1

Published

[![codecov](https://codecov.io/gh/TEHIK-EE/tedi-design-system/graph/badge.svg?token=NKNNJSG19D)](https://codecov.io/gh/TEHIK-EE/tedi-design-system) [![semantic-release](https://img.shields.io/badge/semantic--release-e10079?logo=semantic-release)](https://

Downloads

3,213

Readme

TEDI Design System for Angular

codecov semantic-release

@tedi-design-system/angular is a library of Angular components implementing the TEDI Design System.
It provides reusable, accessible, and consistent UI components to streamline building Angular applications.

Usage instructions and detailed documentation can be found in the TEDI Design System wiki.


Installation

Install the dependencies for your Angular library:

npm run i

Development Guide

Running Storybook

To view and develop components in isolation, start Storybook for Angular:

npm run start

Angular Version Support

The library supports the three latest Angular major versions. Angular releases a new major every 6 months and deprecates versions after 18 months. See the Angular release schedule for upcoming dates.

Currently supported: Angular 19, 20, 21

CI runs build and test jobs against all supported versions using a matrix strategy. The base version (used for npm ci) is determined by devDependencies in package.json — the other versions are installed on top via ng update.

Adding a new Angular version

When a new Angular major is released (e.g. v22):

  1. package.json — add || ^22.0.0 to every Angular peer dependency and ngx-float-ui
  2. .github/workflows/angular-test-and-lint.yml — add 22 to the angular-version matrix in the build and test jobs
  3. .github/workflows/angular-release.yml — add 22 to the angular-version matrix in the test job

Dropping a deprecated Angular version

When an Angular major reaches end-of-life (e.g. v19):

  1. package.json — remove ^19.0.0 || from every Angular peer dependency and ngx-float-ui
  2. .github/workflows/angular-test-and-lint.yml — remove 19 from the angular-version matrix in the build and test jobs
  3. .github/workflows/angular-release.yml — remove 19 from the angular-version matrix in the test job
  4. Bump devDependencies to the new minimum supported Angular version so the library is always built and developed against a supported release

Contributing

Check the wiki for component guidelines and coding standards. Report issues or contribute via GitHub Issues.


Visual Testing

We use Chromatic for visual testing, reviewing UI changes, and preventing visual regressions.