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

neobrutalistcomponents

v0.2.1

Published

Brutalist React components. Four flavors. One switch.

Readme

neobrutalistcomponents

Brutalist React components. Four flavors. One switch.

npm install neobrutalistcomponents
import { NeoProvider, Button } from 'neobrutalistcomponents';
import 'neobrutalistcomponents/neobrutalistcomponents.css';
import 'neobrutalistcomponents/themes/classic.css';

export function App() {
  return (
    <NeoProvider theme="classic">
      <Button>Click me</Button>
    </NeoProvider>
  );
}

Themes: classic · tech · swiss · y2k — import only the ones you use.

Components in v0.2: Button, Input, Card.

Live demo: https://sssamuelll.github.io/neobrutalistcomponents

Fonts

Each theme expects specific font families. The library does not load any fonts — you're responsible for making them available. Easiest option is the Google Fonts CDN via <link> tags in your index.html:

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800;900&family=Inter+Tight:wght@400;500;600;700;800;900&family=Space+Grotesk:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;600;700&family=Geist+Mono:wght@400;500;600;700&family=VT323&family=Sixtyfour&family=Bungee+Shade&display=swap" />

Or self-host via @fontsource. Per theme:

| Theme | Families | | -------- | ------------------------------------------------- | | classic | Inter + Space Grotesk + JetBrains Mono | | tech | Geist Mono + JetBrains Mono | | swiss | Inter Tight (Helvetica Neue stand-in) + JetBrains | | y2k | VT323 + Sixtyfour + Bungee Shade |

If you load only the themes you use, you can trim the family list accordingly.

Development

npm install      # once
npm run dev      # run the landing/playground
npm run test     # run component tests
npm run build    # build lib + site

License

MIT — see LICENSE.