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

nirengi-ui-kit

v0.1.5

Published

A modern, professional Angular UI Kit library providing reusable, themeable components for building complex applications.

Readme

Nirengi UI Kit

A modern, professional Angular UI Kit library providing reusable, themeable components for building complex applications.

Features

  • Angular 18+ and 20 compatible
  • Standalone components (no NgModule required)
  • Tailwind CSS 3 integration
  • Tree-shakable builds with explicit imports
  • TypeScript strict mode and full typing
  • BEM + Tailwind style methodology
  • Design token driven system
  • Accessibility-minded (WCAG 2.1 AA guidance)
  • Responsive and mobile-first

Installation

Install via npm:

npm install nirengi-ui-kit

Usage

This library avoids barrel files (index.ts). Import components, enums and tokens via their direct paths to ensure guaranteed tree-shaking and minimal bundle sizes.

Example: Enums

import { Size } from 'nirengi-ui-kit/common/enums/size.enum';
import { ColorVariant } from 'nirengi-ui-kit/common/enums/color-variant.enum';

const buttonSize = Size.Medium;
const buttonVariant = ColorVariant.Primary;

Example: Types

import { SizeType, SizeValue } from 'nirengi-ui-kit/common/types/size.types';
import { ColorVariantType } from 'nirengi-ui-kit/common/types/color.types';

const size: SizeType = 'md';
const variant: ColorVariantType = 'primary';

Design Tokens

import { designTokenColors } from 'nirengi-ui-kit/design-tokens/colors';
import { designTokenSpacing } from 'nirengi-ui-kit/design-tokens/spacing';

const primary600 = designTokenColors.primary['600'];
const spacing4 = designTokenSpacing['4']; // '1rem'

Components (examples)

import { ButtonComponent } from 'nirengi-ui-kit/components/button/button.component';
import { InputComponent } from 'nirengi-ui-kit/components/input/input.component';
import { ModalComponent } from 'nirengi-ui-kit/components/modal/modal.component';

Development

Use path aliases during development for convenience. Consumers should always import from the package paths.

// Inside the library (dev)
import { Size } from '@common/enums/size.enum';

// Consumer usage
import { Size } from 'nirengi-ui-kit/common/enums/size.enum';

Build

ng build nirengi-ui-kit
ng build nirengi-ui-kit --configuration production

Test

ng test nirengi-ui-kit
ng test nirengi-ui-kit --code-coverage

Documentation & Architecture

Principles:

  1. Standalone components — no NgModule required.
  2. Signals API for reactive state.
  3. Zoneless-first design (no runtime dependency on Zone.js).
  4. BEM class names combined with Tailwind utility usage via @apply.
  5. Explicit exports and direct imports to guarantee tree-shaking.

Design System — Centralized Size Management

All component sizes (height, padding, text-size, gap, icon-size, border-radius) are centrally managed in projects/nirengi-ui-kit/tailwind.config.js.

Do not hard-code pixel values in component styles; use Tailwind custom classes defined in the config.

Example tailwind extension:

// projects/nirengi-ui-kit/tailwind.config.js
module.exports = {
  theme: {
    extend: {
      height: {
        'component-xs': '24px',
        'component-sm': '32px',
        'component-md': '36px',
        'component-lg': '40px',
        'component-xl': '48px',
      },
      spacing: {
        3.5: '0.875rem',
      },
      colors: {
        /* ... */
      },
      fontFamily: {
        /* ... */
      },
    },
  },
};

SCSS usage (preferred):

.nui-button {
  &--xs { @apply h-component-xs gap-1 px-2 text-xs; }
  &--sm { @apply h-component-sm gap-1.5 px-3 text-sm; }
  &--md { @apply h-component-md gap-1.5 px-3.5 text-sm; }
}

Avoid hard-coded values in components (height: 32px etc.).

Size mapping reference

| Size | Height class | Pixel | Padding | Text | Gap | | ------ | --------------- | ----- | ------- | -------- | ------ | | XSmall | h-component-xs | 24px | px-2 | text-xs | gap-1 | | Small | h-component-sm | 32px | px-3 | text-sm | gap-1.5| | Medium | h-component-md | 36px | px-3.5 | text-sm | gap-1.5| | Large | h-component-lg | 40px | px-5 | text-base| gap-2 | | XLarge | h-component-xl | 48px | px-6 | text-lg | gap-2.5|

Note: common/constants/size.constants.ts is kept for reference only. Source-of-truth values live in tailwind.config.js.

Style Methodology

Use English BEM class names with Tailwind utilities applied via SCSS @apply.

Example HTML/SCSS:

<button class="button button--primary button--medium">
  <span class="button__icon">📌</span>
  <span class="button__text">Save</span>
</button>
.button {
  @apply inline-flex items-center gap-2 rounded-md font-medium transition-colors;

  &--primary { @apply bg-blue-600 text-white hover:bg-blue-700; }
  &--medium { @apply px-4 py-2 text-base; }
  &__icon { @apply h-5 w-5; }
  &__text { @apply truncate; }
}

Contributing

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/amazing
  3. Commit your changes: git commit -m 'feat: add amazing feature'
  4. Push: git push origin feature/amazing
  5. Open a Pull Request

Please follow the project's coding standards and add tests for new features. Open an issue for large design changes before implementation.

License

MIT

Links

  • https://angular.dev
  • https://tailwindcss.com
  • https://www.typescriptlang.org

Made with ❤️ by Nirengi Team