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

@konstantinlindner/cn

v1.0.0

Published

A tiny utility to merge className strings with Tailwind CSS support. The new left-pad! 🎉

Readme

@konstantinlindner/cn

A tiny utility to merge className strings with Tailwind CSS support. The new left-pad! 🎉

A minimal, zero-config utility that combines clsx and tailwind-merge into a single function for managing conditional and Tailwind CSS classes.

Installation

# Using pnpm
pnpm add @konstantinlindner/cn clsx tailwind-merge

# Using npm
npm install @konstantinlindner/cn clsx tailwind-merge

# Using yarn
yarn add @konstantinlindner/cn clsx tailwind-merge

Usage

import { cn } from '@konstantinlindner/cn'

// Basic usage
cn('px-2 py-1', 'bg-blue-500') // 'px-2 py-1 bg-blue-500'

// Conditional classes
cn('px-2', isActive && 'bg-blue-500', 'px-4') // 'bg-blue-500 px-4' (px-2 and px-4 merged)

// With objects
cn({ 'bg-blue-500': isActive, 'text-white': true }) // 'bg-blue-500 text-white'

// Tailwind class deduplication
cn('px-2 py-1', 'px-4') // 'py-1 px-4' (px-2 removed, px-4 wins)

// With arrays
cn(['px-2', 'py-1'], 'bg-blue-500') // 'px-2 py-1 bg-blue-500'

// Handles null/undefined gracefully
cn('px-2', null, undefined, false && 'bg-red', 'py-1') // 'px-2 py-1'

Why?

This is a common pattern in React + Tailwind projects. Instead of copying this utility function into every project, why not make it a package? It's the new left-pad! 😆

Development

# Install dependencies
npm install

# Build
npm run build

# The package will auto-build before publishing
npm publish

License

MIT