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

classname-manager

v1.1.0

Published

🖌️ ClassName Manager to easily handle component variants

Downloads

928

Readme

🖌️ classname-manager

npm version bundle-size

ClassNames manager to easily get classes for component variants

Super tiny manager to merge, extend and dynamically add class names focused on variations

🚀 Features

  • ✅ Super simple and minimalistic
  • 🔑 Type-safe (Typescript)
  • ❌ No more manual matching classes to props or adding types
  • 🧬 TailwindCSS Intellisense support

📦 Install

# NPM
npm install classname-manager

# YARN
yarn add classname-manager

# PNPM
pnpm add classname-manager

💻 Usage example

import { classNameManager } from 'classname-manager'

interface ButtonProps {
  styleType: 'primary' | 'secondary'
  color: 'light' | 'dark'
  disabled: boolean
}

/**
 * Define once the class schema
 * based on possible values from props
 * 
 * @example 
 *  - props: { styleType: 'primary', color: 'light' }
 *    Result: 'btn btn-primary text-black bg-white'
 * 
 */
const getButtonClassName = classNameManager<ButtonProps>({
  base: 'btn',
  dynamicVariants: {
    styleType: {
      primary: 'btn-primary',
      secondary: 'btn-secondary',
    },
    color: {
      light: 'text-black bg-white',
      dark: 'text-white bg-black',
    },
    disabled: {
      true: 'btn-disabled bg-gray'
    }
  }
})


const Button = (props: ButtonProps) => {
  const btnClassName = getButtonClassName(props)

  return (
    <button className={btnClassName}>{props.label}</button>
  )
}

🧬 TailwindCSS Plugin config (VSCode)

In order to allow the tailwindcss plugin intellisense to work properly with classname-manager you will need to add the following code to your settings.json file

// your project > .vscode (folder) > settings.json
{
  "tailwindCSS.experimental.classRegex": [
    [ "cnm([^ç]*?(base\\:|dynamicVariants\\:)+[^ç]*?)\\}\\);?(\r\n|\r|\n)", "[\"'`]([^\"'`]*).*?[\"'`]" ],
    [ "classNameManager([^ç]*?(base\\:|dynamicVariants\\:)+[^ç]*?)\\}\\);?(\r\n|\r|\n)", "[\"'`]([^\"'`]*).*?[\"'`]" ]
  ]
}

📖 Documentation

The package exports 2 names for the main function, both executes the same:

  • classNameManager
  • cnm (Reduced name)

⭐ Initialization

import { cnm } from 'classname-manager'

// By schema object
const getClassName = cnm({ /** Your schema */ })

// By callback returning the schema object
const getClassName = cnm((props) => ({ /** Your schema */ }))

🔖 SCHEMA object properties

All schema properties values can be either a string or an array of strings

🟣 base (string | Array<string>)

Class to be placed at the beginning of the returned value

const getClassName = cnm({ base: 'btn', /*...*/ })
// Result: 'btn (other classes)'

🟣 dynamicVariants (object)

Here is where you define your classes based on props passed in to the function. (For boolean values the expected properties are: true and false)

const getClassName = cnm({
  base: 'btn',
  dynamicVariants: {
    styleType: {
      primary: 'btn-primary',
      secondary: 'btn-secondary',
    },
    enabled: {
      true: 'bg-transparent',
      false: 'bg-gray',
    }
  }
})

getClassName({ styleType: 'secondary' })
// Result: 'btn btn-secondary'

The example above doesn't return any value from the enabled property because it's not passed in the function call. You can handle this by adding a DEFAULT property to the schema object values

- DEFAULT dynamicVariant value
const getClassName = cnm({
  base: 'btn',
  dynamicVariants: {
    styleType: {
      primary: 'btn-primary',
      secondary: 'btn-secondary',
    },
    enabled: {
+     DEFAULT: false,
      true: 'bg-transparent',
      false: 'bg-gray',
    }
  }
})

getClassName({ styleType: 'secondary' })
+ // Result: 'btn btn-secondary bg-gray'

Note: Although you can use the DEFAULT property, it is optional. In most cases it's recommended to initialize props with a default value from js/ts side to have a better control if you need to use it in other places

🟣 dynamicClassNames (object)

In case you need to apply some logic to calculate if some classes should be added, you can add it like the example below:

const getClassName = cnm(({ status }) => {
  const isDisabled = isButtonDisabled(status)
  return {
    base: 'btn',
    dynamicVariants: {
      styleType: {
        primary: 'btn-primary',
        secondary: 'btn-secondary',
      }
    },
    dynamicClassNames: {
      'btn--disabled': isDisabled
    }
  }
})
// -----------------------------------

getClassName({ status: 'triggered' })
// Result: 'btn btn--disabled'

⏬ Returned function

When you define your schema, it returns another function that you can use to get the class names based on the props passed in. You can pass an extra property:

🟣 extraClassNames property (string | Array<string>)

You can add extra classes to the end of the returned value by using the extraClassNames property

interface ButtonProps {
  styleType: 'primary' | 'secondary'
}

const getClassName = cnm<ButtonProps>({
  base: 'btn',
  /* your schema */
})

/**
 * It allows you to pass extra classes at
 * the end of the returned value
 */
getClassName({ styleType: 'primary', extraClassNames: 'font-bold' })
// Result: 'btn btn-primary font-bold'

Created with Typescript! ⚡ and latin music 🎺🎵