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

@pure-simple-tech/frictionless-ui

v0.3.0

Published

A very opinionated ReactJS component library designed for maximum ease of use.

Downloads

17

Readme

frictionless-ui

UI components that are easy to interact with

About

These components are not intended to be used "as is", but rather to be used as building blocks for your own components.

TODO

  • create build script to create a single css file from all the components
  • make export file point to the dist folder (will be created at build time)
  • add build stept to "publish" script
  • setup pre-commit check (husky?) to make sure all commits follow conventional commits
  • make "publish" script auto-increment version based on conventional commits
  • add es-lint
  • add prettier
  • include style and lint checks in "publish" script
  • include style and lint checks in pre-commit hook (make sure they only check staged files)