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

@m10c/mui-kit

v0.0.2

Published

MUI-based admin UI toolkit (theme, form, components, hooks)

Readme

MUI Kit

A shared MUI-based UI toolkit. It provides a configurable theme plus a set of ready-made form fields, components, and hooks, so admin projects share one consistent look and set of building blocks.

import {
  createMuiKitTheme,
  FieldText,
  SeverityPill,
  SubmitButton,
  Toaster,
  usePopover,
} from '@m10c/mui-kit';

Theme

The theme is built in layers, each one overriding the one before it:

  1. MUI defaults — the standard MUI base theme.
  2. The kitcreateMuiKitTheme applies the shared m10c look (palette, shape, component defaults) on top of MUI.
  3. The project — each project takes the kit's theme and layers its own palette, typography, and component overrides on top, so it can diverge where needed while keeping the shared base.

In the simplest case a project just calls createMuiKitTheme and passes the result to MUI's ThemeProvider:

import { createMuiKitTheme } from '@m10c/mui-kit';
import { ThemeProvider } from '@mui/material/styles';

const theme = createMuiKitTheme({ primaryColor: 'indigo' });

<ThemeProvider theme={theme} defaultMode="light">
  <App />
</ThemeProvider>

createMuiKitTheme accepts overrides for the common cases:

createMuiKitTheme({
  primaryColor: 'blue',
  direction: 'rtl', // optional, defaults to ltr
  linkComponent: NextLink, // optional, wires a router link into MuiLink
  paletteOverrides: {
    // optional, deep-merged per color scheme
    light: { background: { default: '#fafafa' } },
    dark: { background: { default: '#101010' } },
  },
});

For anything beyond those options, layer a project theme on top with MUI's own createTheme. This is the third layer — the project keeps the kit's base and overrides only what it needs (here, typography and component styles):

import { createTheme } from '@mui/material/styles';
import { createMuiKitTheme } from '@m10c/mui-kit';

const base = createMuiKitTheme({ primaryColor: 'indigo' });

const theme = createTheme(base, {
  typography: { h1: { fontFamily: "'Plus Jakarta Sans', sans-serif" } },
});

theme.components = projectComponentOverrides; // project-specific MUI overrides

Components, form fields, and hooks

Components are standard MUI-styled React components and take their own props.

Form fields are built for react-typed-form — give each one a form field via its field prop, and it handles value/validation wiring:

import { FieldText, SubmitButton } from '@m10c/mui-kit';

<FieldText field={form.getField('name')} label="Name" />
<SubmitButton form={form}>Save</SubmitButton>