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

tailwind-watch

v0.0.6

Published

A tool to add tailwind to projects easily

Downloads

3,142

Readme

Tailwind Watch

A dead-simple package to intelligently watch your project for Tailwind-specific files and rebuild when they change.

This tool does not install PostCSS, Tailwind, or anything else. Install those yourself and use this tool to watch your files and rebuild when they change.

Why might you use this?

  • You're having difficulty getting Tailwind/PostCSS working in your project
  • You're tired of configuring Tailwind and PostCSS through bundlers like Webpack and Rollup
  • You've evolved past bundlers to Skypack but still want to use Tailwind
  • You want control over all PostCSS and Tailwind via configuration files in your project root
  • You want hands-free watching and building, depending on .env variables and process.env.NODE_ENV

Installation & Usage

First, install the package:

npm i -D tailwind-watch

If you don't already, make sure you've at least got PostCSS and Tailwind installed:

npm i -D postcss postcss-cli tailwindcss

Then, add input and output values to your .env file, or create it if it does not already exist, like so:

TAILWIND_IN=src/input.css
TAILWIND_OUT=dist/output.css

Finally, add the proper commands to your package.json scripts. This works best by tying your existing commands together with something like npm-run-all. Here's an example of how you might tie this package together with Eleventy:

{
  "scripts": {
    "build": "NODE_ENV=production npm-run-all build:*",
    "build:eleventy": "eleventy",
    "build:tailwind": "tailwind-watch",
    "dev": "npm-run-all dev:*",
    "dev:eleventy": "eleventy --serve --quiet",
    "dev:tailwind": "tailwind-watch"
  }
}

This package will do one of two things, depending on the value of process.env.NODE_ENV:

  1. If the value is production, it will ONLY build the output file.
  2. If the value is anything else, it will build the output file AND start the watcher.

Happy Tailwinding!