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

@teacss/inspector

v0.10.11

Published

TeaCSS inspector: the dev-server page @teacss/vite mounts at /__teacss, reading the Rust engine (@teacss/engine)

Readme

@teacss/inspector

The TeaCSS inspector: a page on the development server that shows the resolved project, each module's tokens, the generated CSS and a REPL with completion. Token lookup is an endpoint, not a view: GET /__teacss/api/token/<token> (token percent-encoded) returns one token's match info as JSON. It reads the Rust engine (@teacss/engine) and answers loopback requests only.

You do not install it yourself. @teacss/vite, and so @teacss/astro, depends on it and serves it at /__teacss on the dev server. It never runs in a build. Pass inspector: false to the plugin to turn it off:

// vite.config.ts
import { teacss } from "@teacss/vite";
import { defineConfig } from "vite";

export default defineConfig({ plugins: [teacss({ inspector: false })] });

The package exports createInspectorMiddleware(project), a Connect-compatible middleware over a Project from @teacss/engine, for hosts that mount it themselves.

Documentation