Inspired by babel-plugin-react-css-modules
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.
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>
);
}
}
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 |
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.
- Improve performance
- Add memoization
- Add compile time string to array conversion where possible
- Add tests for
bindStyleName
helper - Add config support
- Make memoization optional
- Make warning optional
MIT