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

@maccman/babel-plugin-transform-jsx-classnames

v1.1.1

Published

className and styleName on steroids

Downloads

5

Readme

babel-plugin-transform-jsx-classnames

Build Status Coverage Status npm downloads

className and styleName on steroids 💪

Usage

Allow you to write jsx classNamess in a simpler way, without having to worry about importing a helper (like classnames). classNames or styleNames attributes take any number of arguments which can be a string, an array or an object (if the value associated with a given key is falsy, that key won't be included in the output). See examples

Install

When babel-plugin-transform-jsx-classnames cannot resolve classNames / styleNames during compilation, it imports a helper function (read build time resolution). Therefore, you must install babel-plugin-react-css-modules as a direct dependency of the project.

$ npm install babel-plugin-transform-jsx-classnames --save

Add to .babelrc:

{
  plugins: ['transform-jsx-classnames']
}

Note: ⚠️ If you're using babel-plugin-react-css-modules, ensure you're adding transform-jsx-classnames before

Build time resolution

The plugin will try to resolve the classNames / styleNames during the compilation (classNames={"foo", { active: true }}) and fallback to runtime if not possible (classNames={_cx("foo", { active: props.active })} - a tiny helper (~0.3Ko) will be included automatically.

Runtime helper

The runtime helper is very similar to the classnames package. It actually behaves like its dedupe version.

The only difference you'll find will be with full numeric classNamess: output will always spit numbers first (ex: classNames={"a", 12} => classNames="12 a"). It shouldn't be a big deal though, as using numeric values for classNamess is pretty rare and order only matters in a very few specific cases.

Performance & dedupe

Dedupe has been optimized a lot and its performance is very similar to classnames (in no dedupe mode). It's even better in some cases.

Examples

Build time

<div classNames={"foo", "bar"}>
→ <div classNames="foo bar"></div>

<div classNames={'foo', { bar: true }}>
→ <div classNames="foo bar"></div>

<div classNames={{ 'foo-bar': true }}>
→ <div classNames="foo-bar"></div>

<div classNames={{ 'foo-bar': false }}>
→ <div classNames=""></div>

<div classNames={{ foo: true }, { bar: true }, ["foobar", "duck"]}>
→ <div classNames="foo bar foobar duck"></div>

<div classNames={'foo', { bar: true, duck: false }, 'baz', { quux: true }}>
→ <div classNames="foo bar baz quux"></div>

<!-- styleNames -->
<div styleNames={"foo", "bar"}>
→ <div styleNames="foo bar"></div>

<!-- Dedupe -->
<div classNames={'foo foo', 'bar', { bar: true, foo: false }}>
→ <div classNames="bar"></div>

<!-- No change -->
<div classNames={props.active ? "foo" : "bar"}>
→ <div classNames={props.active ? "foo" : "bar"}></div>

Runtime

When classNames / styleNames can't be resolved at compilation.

<div classNames={"foo", { active: props.active }}>
→ <div classNames={_cx("foo", { active: props.active })}></div>

<div classNames={{ foo: true, [`btn-${props.type}`]: true }}>
→ <div classNames={_cx({ foo: true, [`btn-${props.type}`]: true })}></div>

<div classNames={"foo", props.active && getClassName()}>
→ <div classNames={_cx("foo", props.active && getClassName())}></div>

Send some love

You like this package?

Buy me a coffee