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-bit/tailwind-smart-config

v0.11.0

Published

Smart tailwind configuration modifier

Readme

@css-bit/tailwind-smart-config

Smart tailwind configuration modifier.

npm github node

Installation

npm install @css-bit/tailwind-smart-config --save-dev

Usage

Tailwind v3:

import { tailwindSmartConfig } from '@css-bit/tailwind-smart-config';

export default {
  plugins: [tailwindSmartConfig()]
};

Tailwind v4: tailwindSmartConfig takes nested options, which v4's @plugin directive cannot express (it only accepts a flat list of declarations), so load it through the @config directive with a v3-style config file instead.

// tailwind.config.js
import { tailwindSmartConfig } from '@css-bit/tailwind-smart-config';

export default {
  plugins: [
    tailwindSmartConfig({
      spacing: { sm: 10, md: 20 },
      unit: 'rpx'
    })
  ]
};
/* app.css */
@import 'tailwindcss';
@config '../tailwind.config.js';

featureFixing takes no options, so it can go straight into @plugin:

@import 'tailwindcss';

@plugin '@css-bit/tailwind-smart-config/fixing.mjs';

Tailwind v4 limitations

These come from v4 itself, not from this plugin:

  • Custom background-size values containing / are not available, e.g. bg-y-2/3 and bg-x-1/10. v4 does not extend background-size through the theme, and it rejects escaped / in addUtilities selectors. Use v4's own arbitrary values (bg-[length:auto_66.67%]) or switch the dash option to avoid slashes. Values without a slash (bg-cover, bg-half) work as usual.
  • Some utilities render differently under v4:
    • Negative margins are emitted as calc(160rpx * -1) instead of -160rpx. Same computed value.
    • border-* also sets border-style, and the directional utilities (border-l and friends) additionally set border-width: 1px. In v3 border-0 border-l leaves border-width: 0; in v4 the border-l wins and the result is 1px.
    • @apply emits utilities in v4's cascade order rather than in the order they were written, so declarations that override each other can resolve differently. rounded-b-0 rounded-r-lg gives a bottom-right radius of 10px in v3 but 0 in v4.
    • v4 keeps every declaration while v3's optimiser drops the ones that end up overridden. The computed result is unaffected.

Related