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

@earendil-works/tailwind-check

v0.1.0

Published

Headless Tailwind v4 semantic linting.

Downloads

96

Readme

tailwind-check

Headless Tailwind v4 semantic linting for application code and CSS.

tailwind-check loads the checked project's Tailwind entry CSS, builds a Tailwind design system in memory, and reports semantic diagnostics for class usage and Tailwind CSS directives.

Requirements

  • Node 24+
  • Tailwind v4 in the project being checked
  • a Tailwind entry CSS file such as src/app.css

tailwind-check resolves tailwindcss from the checked project.

CLI

tailwind-check
tailwind-check --changed
tailwind-check --changed --base origin/main
tailwind-check --entry src/app.css
tailwind-check src/components/button.tsx src/app.css

Options:

  • --cwd <path> project root to lint
  • --config <path> explicit config file
  • --entry <path> Tailwind entry CSS override
  • --changed only lint changed files
  • --base <ref> include <ref>...HEAD in changed-file mode

Config

Auto-discovered config files:

  • tailwind-check.json
  • .tailwind-check.json

Example:

{
  "entry": "src/app.css",
  "roots": ["src"],
  "extensions": [".ts", ".tsx", ".js", ".jsx", ".css"],
  "classAttributes": ["class", "className"],
  "classFunctions": ["cn", "clsx", "cva"],
  "enableClassList": true
}

Supported extraction surfaces

  • class="..."
  • className="..."
  • class={...} static string segments
  • cn(...)
  • clsx(...)
  • cva(...)
  • classList={{ ... }} static object keys
  • @apply ...

Diagnostics

  • tailwind/cssConflict
  • tailwind/suggestCanonicalClasses
  • tailwind/invalidApply
  • tailwind/invalidTailwindDirective
  • tailwind/invalidSourceDirective
  • tailwind/deprecatedAtRule
  • tailwind/invalidConfigPath

Output

path/to/file.tsx:12:5 tailwind/<rule> <message>
  suggestion: <replacement>

Exit codes:

  • 0 no diagnostics
  • 1 diagnostics found
  • 2 infrastructure or config failure

Attribution

tailwind-check is inspired by and partially adapted from Tailwind CSS IntelliSense, which is licensed under the MIT License by Tailwind Labs, Inc. See THIRD_PARTY_NOTICES.md for details.

Library API

import { formatDiagnostic, runTailwindCheck } from "@earendil-works/tailwind-check"

const result = await runTailwindCheck({
  cwd: process.cwd(),
  entry: "src/app.css",
  changed: true,
})

for (const diagnostic of result.diagnostics) {
  console.error(formatDiagnostic(result.cwd, diagnostic))
}

runTailwindCheck(...) returns:

  • cwd
  • configPath
  • entryPath
  • filePaths
  • diagnostics
  • scanMode