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

@saarbyrne/playbook

v1.2380.0

Published

kitman playbook library - standalone with inlined colors

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

saarbyrnesaarbyrne

Keywords

Readme

Playbook

Playbook is the Kitman Labs design system which is built on top of MUI.

This package contains the the code that Kitman layers on top of Material UI to build playbook. Based off the designs in the Playbook Master figma file.

🚧 Note: These docs are a WIP as Playbook is being rolled out accross the product see see the project resources below 🚧

Usage

As a starting point, the Material UI components are themed using a global theme we define in this package which is outlined by the design team.

Playbook is built using the following @mui packages

  • @mui/base
  • @mui/icons-material
  • @mui/lab
  • @mui/material
  • @mui/x-data-grid-pro
  • @mui/x-date-pickers-pro

API documentation for all components are found here

It is not recommended to import material components directly from MUI. This gives playbook the flexibility to add wrapper components to suit Kitman labs needs, or to create universal components whos styles have been overrided. See contribution guidelines

Example, MUI docs would suggest:

import Stack from '@mui/material/Stack';
import Button from '@mui/material/Button';

import { DataGrid } from '@mui/x-data-grid';

But it is reccomended to import via playbook so consistent usage is maintained

import {
  Stack,
  Button,
  DataGrid
} from `@kitman/playbook/components`

Themes

TODO - when the default theme is built, outline how it works here

Components

@kitman/playbook/components houses all the components for:

  • @mui/material
  • @mui/x-data-grid-pro
  • @mui/x-date-pickers-pro

Hooks

This houses utility hooks exported from @mui/material.

Icons

@kitman/playbook/icons is a wrapper for material icons. Usage guidlines are outlined by material ui here. All icons here are available through playbook icons.

Imports can be done via:

import { AccessAlarm, ThreeDRotation } from '@kitman/playbook/icons';

Contribution

The Playbook package is managed by a governance team that spans front-end engineering and design.

Documentation

Playbook uses storybook to document components. Storybook can be run locally or visited on our hosted chromatic instance. See Documentation

Resources