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

css-but-ai

v0.1.0

Published

Vite-first compile-time CSS framework powered by AI prompts in .ass files

Readme

css-but-ai

Vite-first compile-time CSS framework where .ass files contain plain-text prompts.

At load time, the plugin calls a real LLM API, receives CSS, sanitizes it, scopes selectors using a CSS Modules-like naming scheme, and injects the generated CSS through JS.

Current Status

Initial implementation is complete for:

  • .ass import resolution through a Vite plugin
  • Build/dev-time LLM call through OpenAI-compatible chat completions endpoint
  • Strict CSS sanitization with allowlist checks
  • Scoped class name rewriting with format [basename]__[local]__[hash:8]
  • Default export of class map object from each .ass module
  • HMR invalidation on .ass changes

Install

npm install css-but-ai

Usage (Vite)

// vite.config.ts
import { defineConfig } from "vite";
import { assPlugin } from "css-but-ai";

export default defineConfig({
  plugins: [
    assPlugin({
      model: "gpt-4.1-mini",
      apiKey: process.env.OPENAI_API_KEY,
      // endpoint: "https://api.openai.com/v1/chat/completions",
      // timeoutMs: 30000,
    }),
  ],
});
// component.ts
import styles from "./Button.ass";

const className = styles.root;

For TypeScript projects, enable built-in .ass import types once in your tsconfig.json:

{
  "compilerOptions": {
    "types": ["vite/client", "css-but-ai/ass"]
  }
}
# Button.ass
A bold primary button with subtle hover lift, strong contrast text,
12px horizontal padding, rounded corners, and smooth transition.

Environment

Set one of:

  • OPENAI_API_KEY
  • or pass apiKey in plugin options

Safety Model

The sanitizer currently enforces:

  • At-rules allowlist: @media, @supports, @layer
  • Property allowlist from curated defaults
  • Rejects javascript:, expression(), and url() by default

You can override sanitizer values via sanitization plugin option.

Caveats (Current MVP Slice)

  • Uses JS style-tag injection only
  • Does not yet emit dedicated .css assets
  • Relies on model returning strict JSON payload
  • Type declarations for individual class keys are not generated yet

Development

npm run build
npm run typecheck

In-Repo Vite Sample App

A real Vite app is included at examples/vite-app for end-to-end verification.

From the repository root:

npm run sample:install
npm run sample:verify

What sample:verify does:

  • Starts a local mock OpenAI-compatible endpoint
  • Runs a Vite production build in the sample app
  • Compiles a real .ass import through this plugin pipeline

You can also use a live API key in dev mode:

PowerShell:

$env:OPENAI_API_KEY = "your_key_here"
npm run sample:dev

cmd.exe:

set OPENAI_API_KEY=your_key_here
npm run sample:dev

bash/zsh:

export OPENAI_API_KEY=your_key_here
npm run sample:dev

Run both commands in the same terminal session.

Publishing Note

The root .npmignore excludes examples/ so the sample app is never included in published npm package contents.