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

@csszyx/unplugin

v0.15.0

Published

Vite and Webpack integration for csszyx

Readme

@csszyx/unplugin

Vite, Webpack, and esbuild integration for CSSzyx.

Build-time plugin that transforms sz props into Tailwind classes, generates static CSS, optionally mangles class names in production (opt-in), and injects hydration scripts for SSR.

Installation

pnpm add -D @csszyx/unplugin

Or install the umbrella package which includes this:

pnpm add csszyx

Vite

// vite.config.ts
import { defineConfig } from "vite";
import tailwindcss from "@tailwindcss/vite";
import react from "@vitejs/plugin-react";
import csszyx from "csszyx/vite";

export default defineConfig({
  plugins: [...csszyx(), tailwindcss(), react()],
});

The direct import also works:

import csszyx from "@csszyx/unplugin/vite";

Webpack (Next.js)

// next.config.js
const csszyx = require("@csszyx/unplugin/webpack").default;

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    config.plugins.push(...csszyx());
    return config;
  },
};

module.exports = nextConfig;

Webpack (standalone)

// webpack.config.js
const csszyx = require("@csszyx/unplugin/webpack").default;

module.exports = {
  plugins: [...csszyx()],
};

Features

  • sz prop transform -- Compiles sz={{ }} objects into className strings with ONE engine that ships as two artifacts: the native Rust addon (default, through the optional @csszyx/core-* platform package) and the same engine compiled to WebAssembly (shipped inside @csszyx/core, the automatic fallback when the native binary is absent — pin it with build.parser: "wasm").
  • HTML injection -- Injects mangle maps and checksums for SSR hydration
  • HMR support -- Updates styles instantly during development
  • CSS mangling -- Compresses owned class names (e.g., text-center -> z) while retaining names shared with source-visible class/className strings and template quasis
  • File filters -- Top-level include / exclude (glob or RegExp) skip large generated files before the AST budget guard fires; see Config Overview

Class mangling runs in Vite, Webpack, and Rollup final-output hooks. The esbuild adapter supports source transforms and safelist generation but disables class mangling because esbuild does not expose a mutable final-output hook when writing directly to disk; explicit production.mangle: true emits a warning.

Parser selection

The default parser is rust, which runs through the native engine in the matching optional @csszyx/core-* platform package. When that package is missing, the default falls back to the WASM engine and says so once; an explicit build.parser: "rust" fails instead of falling back. Reinstall to pick up the optional dependency for your platform, or set build.parser: "wasm" to choose the WASM engine outright.

Per project:

csszyx({
  build: { parser: "wasm" }, // the engine's WebAssembly build, no native addon
});

Per build:

CSSZYX_PARSER=wasm pnpm build

The default rust path is the native addon; wasm is the same engine compiled to WebAssembly. Both run identical output; only parse speed differs. The former "oxc" and "babel" TypeScript lanes were removed — a config still naming them is ignored like an invalid env value and the build runs on the default.

License

MIT