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

@kolkrabbi/kol-workshop

v0.1.5

Published

KOL workshop/docs system — a handrolled markdown engine, search, tag system (incl. a d3 tag graph), docs viewer, and docs shell. Sits above @kolkrabbi/kol-{theme,icons,component,framework}; content is consumer-injected (the package never globs docs).

Downloads

911

Readme

@kolkrabbi/kol-workshop

The KOL workshop / docs system, lifted from the monorepo apps/web into the design system.

A handrolled documentation engine — no remark, no gray-matter, no fuse.js — plus (in later phases) the docs shell, search, and a tag system including a d3 tag graph. Sits above the other four UI packages and consumes them.

What's in the box

Two entry points:

  • @kolkrabbi/kol-workshop/engine — the pure, React-free, zero-dependency core.
  • @kolkrabbi/kol-workshop — the React layer (docs viewer, shell, tag system) built on the engine.

Engine (/engine)

| Import | What | | --- | --- | | parseDocsMarkdown(md) | block + inline markdown → { sections, toc, introBlocks, inlineTags } | | parseFrontmatter(raw) | YAML-subset frontmatter → object (inline arrays + block lists) | | buildInventory(modules) | a raw-markdown module map → a doc inventory (see the seam below) | | buildInventoryCounts(inv) | status / category / content-type tallies | | getTagColor, extractDocNumber, cleanTitle, groupDocsByMajor, … | doc/tag helpers |

React layer (.)

| Import | What | | --- | --- | | DocumentationReader | the docs viewer — renders one doc from the inventory (article + header + frontmatter + token render) | | ShellLayout, ShellSidebar | the docs shell composition (adapts the DS ShellHeader/ShellDrawer/ShellSearchOverlay) | | TagModeProvider, TagModeGate, TagModeOverlay, TagGraph | the tag system, incl. the d3 tag graph | | WorkshopSidebar, WorkshopDefaultSidebar | example sidebar compositions to copy |

The React layer imports its chrome (Icon/Tag/CodeBlock/Divider/DocsToc from kol-component, ShellHeader from kol-framework) from the DS packages — it keeps no local copies. Chrome CSS ships in @kolkrabbi/kol-theme (kol-components-workshop.css, already in the theme aggregate).

The content-injection seam

The package is Vite-agnostic — it never globs your docs. The consumer owns the import.meta.glob and injects the result as props:

import { buildInventory } from '@kolkrabbi/kol-workshop/engine'
import { DocumentationReader, TagModeProvider } from '@kolkrabbi/kol-workshop'

const modules   = import.meta.glob('/docs/**/*.md', { eager: true, query: '?raw', import: 'default' })
const inventory = buildInventory(modules)
// pass inventory + routes/basePath + docHref(id) + tagHref(tag) into the components

So the package ships the engine + chrome, never the content — bring your own docs.

Tailwind v4 consumers

Tailwind skips node_modules when scanning, so point it at this package's source — otherwise the shell's grid/sidebar/toc layout utilities never generate and the docs shell collapses to a single column:

@source "../node_modules/@kolkrabbi/kol-workshop/src";

Self-check: node src/engine/__check.mjs.