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 🙏

© 2025 – Pkg Stats / Ryan Hefner

tailwind-source-wrapper

v0.0.2

Published

A simple wrapper over tailwind's CLI

Readme

Tailwind Source Wrapper

What it this?

A super tiny (less than 3kB) wrapper over tailwind's CLI that allows to have input&output source files in the tailwind config file.

Motivation

  • scripts section in package.json tend become lengthy and cluttered. I like to have it slim and clean;
  • Tailwind supports config file, but for some reason input&output source files have to be passed as params. I feel like these things can be in config file as well;
  • There is a discussion about exaclty the same idea at Github. And it does have some supporters.

How to set up

The next diff should say for itself

diff --git i/package.json w/package.json
index 6d1fd87..b522015 100644
--- i/package.json
+++ w/package.json
@@ -8,7 +8,7 @@
     "test": "echo \"Error: no test specified\" && exit 1",
     "start": "concurrently 'npm run build:dev' 'npm run live-reload'",
     "build:metadata": "echo \"<!-- Date: $(date -Iseconds), Git: $(git describe --tag --always --dirty='*') -->\n\" > ./wp-content/themes/naszkupon-wp/.build-metadata.php",
-    "build:css-base": "npx tailwindcss -i ./wp-content/themes/naszkupon-wp/input-tw.css -o ./wp-content/themes/naszkupon-wp/styles.v2.css",
+    "build:css-base": "npx tsw",
     "build:dev": "npm run build:metadata && npm run build:css-base -- --watch",
     "build:prod": "npm run build:metadata && npm run build:css-base -- --minify",
     "live-reload": "node --env-file=.env.local node_modules/.bin/browser-sync start --config bs-config.js"
diff --git i/tailwind.config.js w/tailwind.config.js
index 08a68a5..2ebdc71 100644
--- i/tailwind.config.js
+++ w/tailwind.config.js
@@ -1,5 +1,7 @@
 /** @type {import('tailwindcss').Config} */
 module.exports = {
+  input: "./wp-content/themes/naszkupon-wp/input.v2.css",
+  output: "./wp-content/themes/naszkupon-wp/styles.v2.css",
   content: {
     relative: true,
     files: [

Feedback

Have any kind of feedback or contribution - you are welcome.