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

@charitypro/ui-kit

v1.4.3

Published

ProCharity project UI-kit library for common usage through federated bundles

Readme

React UI-library for ProCharity project

Stack:

  • React 18
  • TypeScript 5
  • Dart SASS \ SCSS

Toolset:

  • Yarn + PNP, zero install ready
  • Vite
  • Storybook + Playwright tests
  • ESlint
  • Prettier
  • Husky + lint-staged
  • generate-react-cli configuration

Installation

  1. Clone repository
  2. cd DIR
  3. yarn

Commands

Create new component

yarn gen component Name — place new component files in src/components including CSS module and story.

yarn gen component Name --withLazy=true — like first, but add index.ts file with default lazy export of component for federation, pages and etc.


Run in watch mode

yarn dev — just execute build --watch for rebuild on changes, usefull when this repo used as dependency somewhere else.


Build library

yarn build — required for publishing library or using in other packages as dependency.

yarn build-storybook — used for publishing storybook build somewhere like chromatic.


Check code quality

yarn lint — execute eslint yarn format — format code in src/ yarn test — execute all tests, initial include only storybook tests

Developing

yarn storybook — main development environment.

Do as follows:

  1. generate new component
  2. define prop types
  3. write a story
  4. write a play function for key use cases
  5. develop component while looking to story preview
  6. add more use cases playbooks

Naming conventions

Prefixed names:

  • Layout* — global page Layout, top-level component of every page or screen
  • Section* — second level component under Layout
  • Card* — box content wrapper for column based content presentation

Postfixed names:

  • *Page — top level component for building page including Layout and all under
  • *Screen — middle level component for building large part of page, screen flow, modal content and etc. Don't include top-level Layouts.
  • *Flow — group of screens combined with internal routing logic.