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/postcss

v0.10.11

Published

PostCSS plugin for TeaCSS: replaces the entry's @teacss rule with the CSS the Rust engine generates

Readme

@teacss/postcss

The PostCSS plugin for TeaCSS. In the stylesheet whose top level holds @teacss;, it calls the Rust engine (@teacss/engine) in process and replaces that rule with the generated CSS. It needs Node.js 26 or later and PostCSS 8.

Install

npm install --save-dev @teacss/postcss postcss postcss-cli

postcss-cli is only for the example below; any PostCSS runner works.

Use

// postcss.config.mjs
import teacss from "@teacss/postcss";

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

Configuration lives in the CSS entry. Create index.css:

@presets "standard,icons,official";
@source "./src/**/*.{js,jsx,ts,tsx,html}";
@teacss;

Process the entry and link the output from your pages:

npx postcss index.css -o dist/app.css

The Standard fonts go to teacss-fonts/ beside the output file (dist/teacss-fonts/ here), and the stylesheet links them with relative URLs. Vite and webpack's postcss-loader pass the entry itself as the output file, so the fonts land in teacss-fonts/ beside the entry and the bundler emits them as assets; you may want Git to ignore that directory. Without an output file (PostCSS's to option), the fonts stay inline as data: URLs.

teacss is both the default and a named export.

Documentation