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

@metricsrb/fumablox

v1.0.1

Published

Luau documentation platform: semantic model, Fumadocs API reference, and Roblox developer tooling.

Readme

Fumablox

A documentation and developer-tooling platform for Luau.

Fumadocs is the presentation layer. The product is a compiler: Luau source becomes a semantic model, and that model drives the API reference, search, graphs, validation, coverage, and API diffs.

                    ┌── API reference (Fumadocs MDX)
                    │
Luau ──► parser ────┼── search
                    │
                    ├── require() graphs
                    │
                    ├── API diff
                    │
                    └── check / coverage

MDX ───────────────────► guides / tutorials

You should not have to write a function twice — once in Luau and again in Markdown. Comments enrich the model; they are not the only source of truth.

What it understands

From source, not only from tags:

  • classes / modules / returned tables
  • methods, functions, properties, events
  • export type table types (Takeoff: (self: Aircraft) -> () is a method)
  • type aliases, string-union enums, constants
  • generics and Luau signatures
  • require() edges and circular dependencies
  • wally.toml / wally.lock (packages linked, not mirrored)
  • game:GetService(...), remotes, Rojo Explorer hierarchy
  • Moonwave-compatible --- / --[=[ comments when you want descriptions, examples, and realms

So this:

export type Aircraft = {
    altitude: number,
    speed: number,
    Takeoff: (self: Aircraft) -> (),
}

function Aircraft:Takeoff()
end

becomes an API page with properties, methods, and source links — even if you never wrote @param.

Install

npm install -D @metricsrb/fumablox

npx fumablox init
npx fumablox generate
npm run dev
title = "MyLibrary"
code = ["src"]
outDir = "content/docs/api"

Then: generate, dev, check, coverage, graph, search, diff, extract.

Source: github.com/metricrb/fumablox. Docs: metricrb.github.io/fumablox.

License

MIT