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

fractalsvelte

v0.4.2

Published

A components library for Sveltekit with no Tailwind, no class-string merging, and customisation exposed through props. The docs site lives in `src/routes/docs/`; page content lives in `src/content/components/`.

Readme

Fractalsvelte

A components library for Sveltekit with no Tailwind, no class-string merging, and customisation exposed through props. The docs site lives in src/routes/docs/; page content lives in src/content/components/.

The library still ships from src/lib/ — SvelteKit keeps them separate automatically.

Page structure

  1. <h1 class="doc-title"> + <p class="doc-lede">
  2. Hero <Preview>
  3. Installation — npm install and copy-paste. We ship both.
  4. Usage — import + minimal example
  5. Examples — one <Examples> tabbed area
  6. Props<PropsTable>. Comes after Examples: people look for a working example first and reach for the API reference second.
  7. Theming — the tokens the component reads

Chrome conventions

  • Radius is 3px (--doc-r), or 6px (--doc-r-lg) for large surfaces — preview frames, tables, cards, drawers. Nothing rounder, and no single-side accent borders: they look wrong where the accent meets a rounded corner.
  • Prose selectors must exclude [data-slot]. docs.sass styles p, a, ul, code inside .doc-article, and a rendered component sits inside that scope. <Button href> is an <a> and picked up the prose underline until the selector became a:not([data-slot]). Every new prose rule needs the same exclusion.
  • Chrome components live in src/lib/docs/: Preview, Examples, PropsTable, CodeBlock, Sidebar, Toc.

Dual distribution

The package is published to npm and meant to be copy-pasteable. These conflict: a component .sass that says +interactive breaks when the folder is copied alone. A flattened copy-paste variant (mixins inlined, shared classes resolved) must be generated from the same source — never maintained by hand.