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

@shakka/charma-ui

v3.0.0

Published

A styled Angular component library.

Readme

Charma UI

Angular component library for Charma interfaces. It includes reusable standalone components, directives, SCSS design tokens, themes, icons, and packaged assets.

Visit Charma UI for live demos and comprehensive documentation.

Installation

Install the package in an Angular application:

npm install @shakka/charma-ui

Add the global stylesheet to the app styles array:

"styles": [
  "node_modules/@shakka/charma-ui/charma-ui.scss"
]

Optional theme overrides should be added after charma-ui.scss so they can override the default :root custom properties:

"styles": [
  "node_modules/@shakka/charma-ui/charma-ui.scss",
  "node_modules/@shakka/charma-ui/themes/black.scss"
]

Basic Usage

Import components from @shakka/charma-ui:

import { Button, Alert } from '@shakka/charma-ui';

Use them in a standalone component:

import { Component } from '@angular/core';
import { Button, Alert } from '@shakka/charma-ui';

@Component({
  selector: 'app-example',
  standalone: true,
  imports: [Button, Alert],
  template: `
    <charma-alert type="success">Saved successfully</charma-alert>
    <charma-button label="Continue"></charma-button>
  `,
})
export class ExampleComponent {}

Contents

The library exposes components such as:

  • Accordion, Alert, Avatar, Badge, Breadcrumb
  • Button, Card, Checkbox, Chip, Date Picker
  • Drawer, Dropdown, Empty State, File Upload
  • Input, Menu, Modal Dialog, Pagination, Popover
  • Select, Snackbar, Table, Tabs, Tooltip
  • Tree, Navbar, Price, and more

The public API is defined in src/public-api.ts.

Styles and Assets

The SCSS entrypoint is:

src/charma-ui.scss

It includes the default Charma theme custom properties and public utility classes for typography, spacing, layout, grid, flex, elevation, composition, buttons, icons, and animations.

The default theme included by charma-ui.scss is dark.

Additional theme overrides live under:

src/themes

The stylesheet does not reset consumer application elements globally.

Library assets are packaged from:

src/lib/assets

Local Development

From the workspace root:

npm install
npm run build:lib
npm run storybook

Build output is generated in:

dist/charma-ui

Tests

Run unit tests from the workspace root:

npm test

Maintenance

When adding a component, make sure it is exported from:

src/public-api.ts

The workspace provides a helper:

npm run update:api