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

ui-base

v0.0.1

Published

Base set of React Components

Readme

Components

# run
npm start

Goal

Create reusable components to be used by all my projects. No more recreating the wheel

Features

  • Themable
  • Platform agnostic
  • configurable
  • Custom renderer
  • Component hooks
  • Event orchestration
  • CSS global rules

Rules

  • Must follow jsStandard and Airbnb rules
  • Components must be ES6
  • styles must be localized
  • All components must be composed of primatives

Agnostic

Components are target agnostic. They can be rendered in:

  • Dom
  • native
  • Canvas

This is done using webpack aliases and primitive components that map to correct targets.

Example: the component maps to in Dom and to in native

themable

Custom styles can be overridden via componentrc config by providing path

Todo

  • figure out how postCSS can map to inline
  • remove classes creation from component creation
  • .componentrc must be read from consumers project
  • Component stamper + test stamper yeoman
  • Theme stamper - generate empty style sheets automatically. Work on alias to ignore empties