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

v0.5.2

Published

TeaCSS config loader — discovers the CSS entry and resolves its directives into a config (no teacss.config file).

Readme

@teacss/config

Discovery and parsing for TeaCSS CSS-entry configuration.

TeaCSS has no teacss.config.* file. Entry discovery checks package.json#teacss.entry, index.css, then src/index.css.

@preset "standard";
@source "./src/**/*.{ts,tsx}";
@custom {
  --color-brand-500: #58a6ff;
}
@teacss;

The built-in preset names are standard, shortcuts, and icons. Shortcuts does not enable Standard. Package and local-file preset specifiers are also supported.

import { createRecoveryConfigLoader } from "@teacss/config";

const loadConfig = createRecoveryConfigLoader();
const { config, sources } = await loadConfig(process.cwd());

sources contains the CSS entry, imported and sourced CSS, package preset entry files, and static local preset dependency graphs. Build integrations watch this list. Package dependency trees and dynamic imports are excluded. Local preset entries may use top-level await; transitive dependencies must stay synchronous and statically discoverable.

The recovery loader keeps the last valid configuration during temporary edit errors. Recovery state is isolated by entry path or inline-config identity, and missing dependency candidates remain in sources so file creation can trigger a retry. Failed loads also retain imported stylesheets, resolved package entries, and dependencies found before a later specifier failed to resolve.

Local preset transforms use a bounded content-addressed cache under the nearest node_modules/.cache/teacss/preset-transform. Set TEACSS_PRESET_TRANSFORM_CACHE=false to disable it.

Lower-level APIs:

| API | Purpose | | ------------------------------------- | ------------------------------------------------------------ | | resolveEntryConfig | Resolves an entry and returns its source graph. | | entryDiscoveryFiles | Lists files an integration should watch for entry selection. | | getConfigSourcesFromError | Recovers bounded source candidates from a failed load. | | parseEntry | Parses a complete CSS entry. | | scanTopLevelAtRules | Finds top-level TeaCSS directives safely. | | scanCustomBlocks / diagnoseCustom | Parses and diagnoses @custom blocks. |

This package does not scan application modules, generate CSS, or manage a build tool's lifecycle.

Pre-1.0. Keep behavior aligned across build, CLI, and editor integrations.