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

@macromackie/oss-web

v0.2.0

Published

Shared styles and React components for small OSS documentation sites.

Downloads

899

Readme

@macromackie/oss-web

Shared CSS and React components for Next.js sites using Fumadocs 16 and Tailwind CSS 4.

npm install --save-exact @macromackie/oss-web

Import the stylesheet once in your root layout. It includes Tailwind, the Fumadocs presets, and the shared fonts. Remove duplicate imports of those styles from the application.

import '@macromackie/oss-web/styles.css';
import { SiteHeader, PageFooter } from '@macromackie/oss-web';

export function Page() {
  return <>
    <SiteHeader name="tenet">
      <a href="/docs">Docs</a>
      <a href="https://github.com/macromackie/tenet">GitHub</a>
    </SiteHeader>
    <main id="nd-page" className="home">
      <h1>tenet</h1>
    </main>
    <PageFooter><a href="/llms.txt">llms.txt</a></PageFooter>
  </>;
}

SiteHeader accepts a product name, an optional home href, and navigation children. PageFooter renders its children with the shared footer styles. Both work as React server components. Keep page content, navigation, release metadata, and deployment in the application. Import local CSS after the shared stylesheet for overrides.

PatchDiff renders each file in a Git patch with Pierre Diffs in the shared light style. It is an async server component: highlighting happens during rendering, and the browser receives static markup.

import { PatchDiff } from '@macromackie/oss-web/diffs';

<PatchDiff patch={gitDiffText} />

MIT licensed.