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 🙏

© 2024 – Pkg Stats / Ryan Hefner

tw-variants

v0.1.1

Published

Tailwind variant grouping without increase in css size

Downloads

1

Readme

Introduction

Tailwind doesn't support variant-grouping out of the box because it leads to tons of duplicate CSS being generated as compared to using individual classes (as we can see in this tweet)

This is because with the grouped syntax like focus:(font-bold underline) each group leads to a new CSS selector being generated, and the CSS generated for focus:font-bold and focus:underline can't be reused.

tw-variants overcomes this by expanding this grouped syntax at build time into individual classes. So now when tailwind scans the files, it sees focus:(font-bold underline) as focus:font-bold focus:underline since it has been expanded before tailwind sees it.

This way you can use grouped-syntax while not having to worry about the css size.

Installation

npm install tw-variants

Add the babel plugin to your babel config (.babelrc) :-

{
  "plugins": ["tw-variants/babel"]
}

Add .tw-variants to your .gitignore. This is where tw-variants stores the expanded CSS for tailwind to scan

.tw-variants

And add the same to the content section of your tailwind.config.js:-

module.exports = {
  content: [
    // ...
    './.tw-variants',
  ],
  // ...
};

Usage

Just import tw from tw-variants and use it like a tagged template literal :-

import { tw } from 'tw-variants';

const button = tw`font-semibold border rounded focus:(font-bold underline)`;

You can't use ${variable} inside tw, so instead of doing:-

import { tw } from 'tw-variants';

const button = tw`font-semibold border rounded focus:(font-bold underline)`;
const redButton = tw`${button} bg-red-500`;

Instead do:-

import { tw } from 'tw-variants';

const button = tw`font-semibold border rounded focus:(font-bold underline)`;
const redButton = `${button} ${tw`bg-red-500`}`;

Tailwind CSS IntelliSense

If you're using the "Tailwind CSS IntelliSense" Visual Studio Code extension, you can enable autocompletion inside tw by adding the following to your settings.json:

{
  "tailwindCSS.experimental.classRegex": ["tw`([^`]*)"]
}