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

react-css-modules.macro

v0.1.5

Published

Babel macro for binding css modules to styleName attribute

Downloads

3

Readme

react-css-modules.macro

Babel Macro

Inspired by babel-plugin-react-css-modules

🙌 Motivation

With the support of CSS Loader - CSS modules became a common use case, especially in Create React App. One of the downsides is that you are forced to access styles map via object keys which is not so handy.

import React, { Component } from 'react';
import styles from './Button.module.css'; // Import css modules stylesheet as styles
import './another-stylesheet.css'; // Import regular stylesheet

class Button extends Component {
  render() {
    // reference as a js object
    return <button className={styles.error}>Error Button</button>;
  }
}

One of the solutions is using the babel-plugin-react-css-modules but you either need to eject or rewire.

Since CRA support babel-plugin-macros - we can take advantage of that and still have styleName attribute be mapped to imported CSS modules.

📦 Usage

import { macro } from 'react-css-modules.macro';
import React, { Component } from 'react';
import styles from './Button.module.css';
import './another-stylesheet.css';

macro(styles)

class Button extends Component {
  render() {
    return (
      <button className="some_global_style" styleName="styles-file-style">
        Error Button
      </button>
    )
  }
}

Will be converted to

import _bindStyleNames from "react-css-modules.macro'/dist/bindStyleName";
import React, { Component } from 'react';
import styles from './Button.module.css'; // Import css modules stylesheet as styles

import './another-stylesheet.css'; // Import regular stylesheet

const _getStyleName = _bindStyleNames(styles);

class Button extends Component {
  render() {
    return (
      <button className={"some_global_style" + _getStyleName("styles-file-style")}>
        Error Button
      </button>
    );
  }

}

⚙️ Config

babel-plugin-macros support a configuration for every separate macro in your project. The easiest way to specify it is to add a section to the package.json

"babelMacros": {
    "reactCssModulesMacro": { "option": "value" }
  },

| Option | Type | Default value | Description | :--------- | :------ | :------------ | :---------- | enableMemo | boolean | true | Select whether use memoization or not | targetTag | string | "styleName" | Allow usage of custom tag name instead of styleName | warning | boolean | false | Enable/disable warning messages

🐝 Performance

In simple words, performance is similar to what you would do by having a function that will accept the string of classnames and will convert it to the hashed classnames. (Input -> split(' ') -> map -> find each hashed name -> join(' '). This is basically what the injected helper function getStyleName() will do. There is no build-time optimization here. But there is optional runtime optimization achieved with memoization. I used the package memoizee to do such a thing. Memoization can be turned off/on using the config.

🛣 Roadmap

  • [ ] Improve performance
    • [x] Add memoization
    • [x] Add compile time string to array conversion where possible
  • [ ] Add tests for bindStyleName helper
  • [x] Add config support
    • [x] Make memoization optional
    • [x] Make warning optional

🗒 License

MIT