classname-variants
Stitches-like variant API for plain class names.
The library is framework-agnostic and can be used with any kind of CSS flavor.
It is especially useful though if used with Tailwind or CSS Modules in combination with SolidJs, as it provides some dedicated helpers and even allows for a styled-components like API, but with class names instead of styles!
Basics
Let's assume we want to build a button component with Tailwind CSS that comes in different sizes and colors.
It consists of some base classes that are always present as well as some optional classes that need to be added depending on the desired variants.
const button = variants({
base: "rounded text-white",
variants: {
color: {
brand: "bg-sky-500",
accent: "bg-teal-500",
},
size: {
small: "px-5 py-3 text-xs",
large: "px-6 py-4 text-base",
},
},
});
The result is a function that expects an object which specifies what variants should be selected. When called, it returns a string containing the respective class names:
document.write(`
<button class="${button({
color: "accent",
size: "large",
})}">
Click Me!
</button>
`);
Advanced Usage
Boolean variants
Variants can be of type boolean
by using "true"
as the key:
const button = variants({
base: "text-white",
variants: {
rounded: {
true: "rounded-full",
},
},
});
Compound variants
The compoundVariants
option can be used to apply class names based on a
combination of other variants.
const button = variants({
variants: {
color: {
neutral: "bg-gray-200",
accent: "bg-teal-400",
},
outlined: {
true: "border-2",
},
},
compoundVariants: [
{
variants: {
color: "accent",
outlined: true,
},
class: "border-teal-500",
},
],
});
Default variants
The defaultVariants
option can be used to select a variant by default:
const button = variants({
variants: {
color: {
neutral: "bg-gray-200",
accent: "bg-teal-400",
},
},
defaultVariants: {
color: "neutral",
},
});
SolidJS
The library contains utility functions that are useful for writing SolidJS components.
It works much like variants()
but instead of a class name string, the
resulting function returns an object with props.
import { variantProps } from "@muxit-studio/classname-variants/solid";
const buttonProps = variantProps({
base: "rounded-md text-white",
variants: {
color: {
brand: "bg-sky-500",
accent: "bg-teal-500",
},
size: {
small: "px-5 py-3 text-xs",
large: "px-6 py-4 text-base",
},
rounded: {
true: "rounded-full",
},
},
defaultVariants: {
color: "brand",
},
});
This way a component's props (or part of them) can be directly spread into the
target element. All variant-related props are used to construct the class
property while all other props are passed through verbatim:
type Props = JSX.IntrinsicElements["button"] &
VariantPropsOf<typeof buttonProps>;
function Button(props: Props) {
return <button {...buttonProps(props)} />;
}
function App() {
return (
<Button size="small" color="accent" onClick={console.log}>
Click Me!
</Button>
);
}
💅
Bonus: styled-components, but for static CSS Things can be taken even a step further, resulting in a styled-components like way of defining reusable components. Under the hood, this does basically the same as the example above, but also handles refs correctly:
import { styled, tw } from "@muxit-studio/classname-variants/solid";
const Button = styled("button", {
variants: {
size: {
small: tw`text-xs`,
large: tw`text-base`,
},
},
});
Again, this is not limited to tailwind, so you could do the same with CSS modules:
import { styled } from "@muxit-studio/classname-variants/solid";
import styles from "./styles.module.css";
const Button = styled("button", {
variants: {
size: {
small: styles.small,
large: styles.large,
},
},
});
Note You can also style other custom SolidJS components as long as they accept a
class
prop.
Styled components without variants
You can also use the styled
function to create styled components without any
variants at all:
import { styled } from "@muxit-studio/classname-variants/solid";
const Button = styled(
"button",
"border-none rounded px-3 font-sans bg-green-600 text-white hover:bg-green-500"
);
Polymorphic components with "as"
If you want to keep all the variants you have defined for a component but want to render a different HTML tag or a different custom component, you can use the "as" prop to do so:
import { styled } from "@muxit-studio/classname-variants/solid";
const Button = styled("button", {
variants: {
//...
},
});
function App() {
return (
<div>
<Button>I'm a button</Button>
<Button as="a" href="/">
I'm a link!
</Button>
</div>
);
}
cn
The cn method is a utility function introduced to help clean up CSS class names that are expressed as template literals. As class names are often dynamically generated or manipulated, this can sometimes lead to unwanted white spaces, empty class names, or even boolean and null values being injected into your class strings. This function is designed to prevent these issues and ensure that only valid CSS class names are returned.
import { cn } from "@muxit-studio/classname-variants"; // or "@muxit-studio/classname-variants/solid"
let template = ` myClass1 myClass2 false null `;
let cleanedClassNames = cn(template);
// cleanedClassNames will now be 'myClass1 myClass2'
Tailwind IntelliSense
In order to get auto-completion for the CSS classes themselves, you can use the Tailwind CSS IntelliSense plugin for VS Code. In order to make it recognize the strings inside your variants-config, you have to somehow mark them and configure the plugin accordingly.
One way of doing so is by using tagged template literals:
import { variants, tw } from "@muxit-studio/classname-variants";
const button = variants({
base: tw`px-5 py-2 text-white`,
variants: {
color: {
neutral: tw`bg-slate-500 hover:bg-slate-400`,
accent: tw`bg-teal-500 hover:bg-teal-400`,
},
},
});
You can then add the following line to your settings.json
:
"tailwindCSS.experimental.classRegex": ["tw`(.+?)`"]
Note The
tw
helper function is just an alias forString.raw
.
In order to get type coverage even for your Tailwind classes you can use a tool like tailwind-ts.
License
MIT
Acknowledgement
Thanks to @fgnass for this library :)