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

parse-tailwind-modifier

v1.0.6

Published

Allows an easier way to write dynamic and responsive styling with Tailwind CSS

Downloads

8

Readme

Parse Tailwind Modifier

Allows an easier way to write dynamic and responsive code in Tailwind CSS

Installation:

npm i parse-tailwind-modifier

Usage:

instead of:

   <button
      className={`bg-blue-500 text-white px-4 py-2 rounded-md hover:bg-blue-700 transition-all duration-300
                 sm:bg-green-500 sm:hover:bg-green-700 sm:text-gray-800
                 md:bg-yellow-500 md:hover:bg-yellow-700 md:text-gray-800
                 lg:bg-indigo-500 lg:hover:bg-indigo-700 lg:text-gray-800
                 dark:bg-gray-800 dark:hover:bg-gray-600 dark:text-white`}
    >
      Click me
    </button>

you can write:


import parseTailWindModifier from "./parse-tailwind-modifier";

   <button
      className={`bg-blue-500 text-white px-4 py-2 rounded-md hover:bg-blue-700 transition-all duration-300
                 ${parseTailwindModifier("sm","bg-green-500 hover:bg-green-700 text-gray-800")}
                 ${parseTailwindModifier("md","bg-yellow-500 hover:bg-yellow-700 text-gray-800")}
                 ${parseTailwindModifier("lg","bg-indigo-500 hover:bg-indigo-700 text-gray-800")}
                 ${parseTailwindModifier("dark","bg-gray-800 hover:bg-gray-600 text-white")}`}
    >
      Click me
    </button>

"But I dislike functions with such long names!"

Of course, if you feel the function name is too long you can import like this:

import parseTailWindModifier as ptm from "./parse-tailwind-modifier"; // or any other name you want to give the function

   <button
      className={`bg-blue-500 text-white px-4 py-2 rounded-md hover:bg-blue-700 transition-all duration-300
                 ${ptm("sm","bg-green-500 hover:bg-green-700 text-gray-800")}
                 ${ptm("md","bg-yellow-500 hover:bg-yellow-700 text-gray-800")}
                 ${ptm("lg","bg-indigo-500 hover:bg-indigo-700 text-gray-800")}
                 ${ptm("dark","bg-gray-800 hover:bg-gray-600 text-white")}`}
    >
      Click me
    </button>

Nested Usage:

you can even use it like this:


import parseTailWindModifier from "./parse-tailwind-modifier";

   <button
      className={`bg-blue-500 text-white px-4 py-2 rounded-md hover:bg-blue-700 transition-all duration-300
                 ${parseTailwindModifier("sm",`bg-green-500 ${parseTailwindModifier("hover","bg-green-700 underline scale-150")} text-gray-800`)}`}
    >
      Click me
    </button>

Advantages:

# Less repeated code (well, obviously)

# Nesting possible

# No need to alter tailwind.config.js

# Readable for anyone reviewing the code even if not familiar with this package

Syntax:

Deliberately based on Tailwind syntax:

  1. The first argument is the modifier as a string,
  2. The second argument is the classes you want to append to said modifier as a string with spaces between them.