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

light-classnames

v1.0.1

Published

A light implementation of the classnames/clsx packages with typescript support

Downloads

35

Readme

light-classnames

This package is a very-light (typescript written) substitute to the classnames & clsx packages with only the most important and commonly used features implemented in order to keep it the fastest:

  • literal string that will always be included.
  • objects where the key defines the className and the value represents whether to include the className or not.
  • null and undefined values are ignored.
  • number will be included if it is not a 0.

Because of this, all the examples shown in the original classNames README.md file will work here too.

// esm importing
import  lcn  from  'light-classnames';
// cjs importing
const  lcn = require('light-classnames');
// or include the script tag and it will be included globally
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/bundle.umd.min.js"></script>

lcn('foo', 'bar'); // => 'foo bar'
lcn('foo', { bar:  true }); // => 'foo bar'
lcn({ 'foo-bar':  true }); // => 'foo-bar'
lcn({ 'foo-bar':  false }); // => ''
lcn({ foo:  true }, { bar:  true }); // => 'foo bar'
lcn({ foo:  true, bar:  true }); // => 'foo bar'
// lots of arguments of various types
lcn('foo', { bar:  true, duck:  false }, 'baz', { quux:  true }); // => 'foo bar baz quux'
// other falsy values are just ignored
lcn(null, false, 'bar', undefined, 0, 1, { baz: null }, ''); // => 'bar 1'

Breaking from the original package

why?

I started working on the project after noticing that the bundle size and the amount of features classnames offers is quite big. In my experience working in a large team developing react apps, There was no need for the nested-array functionality and for boolean values. Moreover, the need for binding and dedup was not really there for me and my friends. Combining this with me wanting a passion project of an npm-library and typescript this is what came up!

what?

In order to keep the package light and satisfy the vast majority of the usage of the package, This package (in its base form, without plugins) will only parse literal string, number, object, null and undefined.

This means that array, boolean and any other value will not be parsed by this. More than that, special functionality like binding and dedup will not be here. The original classnames package will do the job greatly!