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

@noxlovette/material

v0.10.9

Published

A Material Design 3 component library for Svelte, built on Bits UI.

Readme

@noxlovette/material

Google's Material Design 3 system, built for Svelte.

Every component is a real MD3 citizen — the token vocabulary (color roles, typescale, elevation, shape, motion), the state layers, the canonical layouts — implemented on top of Bits UI's headless primitives and styled with tailwind-variants. You get the accessibility and interaction behavior Bits UI already gets right, with Material's actual look and feel on top.

npm version npm downloads CI license: MIT

📖 Docs & overview · 🧩 Storybook — browse every component live

Storybook is the canonical place to actually look at things: every component, every variant, with Controls to poke at props and an a11y panel to check contrast and roles as you go. The docs site is prose — install steps, theming, rationale — and links out to Storybook rather than re-implementing a gallery of its own.

Install

npm i @noxlovette/material
/* your root stylesheet */
@import 'tailwindcss';
@import '@noxlovette/material/styles';
@import '@noxlovette/material/theme/light';
@import '@noxlovette/material/theme/dark';
<script lang="ts">
  import { App, Button, Card, Title } from '@noxlovette/material';
</script>

<App>
  <Card class="p-4">
    <Title>Hello world</Title>
    <Button>Click me</Button>
  </Card>
</App>

App wires up theming, dark-mode detection, and icon loading. Dynamic theming (generate a whole MD3 theme from a source color or an image, toggle light/dark/contrast at runtime) is covered on the docs site, along with the SSR setup that avoids a flash of unstyled content.

What's inside

Buttons, cards, dialogs, navigation rail/bar, side sheets, snackbars, tabs, sliders, chips, menus, text fields, and the rest of the MD3 component set, plus Pane/PaneGrid for Material's canonical layouts (list-detail, supporting-pane, feed) without hand-rolling flex/sticky positioning yourself. The full list, with live previews, is in Storybook.

A Claude Code skill ships alongside the library — npx @noxlovette/material material-claude-skill installs it into .claude/skills/material-design, so an agent working in your app gets the same token vocabulary and variant-selection rules this library was built with.

Credits

  • Material Design 3 — the design system itself. All token names, color roles, and layout patterns here are Google's, not reinvented.
  • Bits UI — the headless primitives underneath every interactive component. This library owes its accessibility behavior and interaction correctness to it; ours is the Material skin on top.

Contributing

bun run dev              # showcase site: landing page + prose docs
bun run storybook        # component workbench — the canonical way to view/QA components
bun run check             # svelte-check + tsc
bun run test              # vitest

See CLAUDE.md for the fuller architecture rundown and known pitfalls.

License

MIT