Neurophysiologically Pseudoscientific Manatee

    TypeScript icon, indicating that this package has built-in type declarations

    1.2.2 • Public • Published

    BEM React Helper

    Travis npm

    A helper making it easier to name React components according to BEM convention.


    There are two main entities in BEM: “blocks” and “elements”. Also there are “modifiers” that can change that ones in some ways. And there are relations between the entities — “mixes”. All of them are ruled by CSS classes, and this is where the pain come from.

    There're no any native tools in React (or JSX, or even HTML and CSS) to write BEM-related code. So, developers usually write CSS classes using conditions:

    export default class Block extends Component {
      render() {
        const classes = ['block'];
        if (this.props.visible) classes.push('block_visible');
        if (this.props.type) classes.push(`block_type_${this.props.type}`);
        if (this.props.size) {
        } else {
        if (this.props.mix) classes.push(this.props.mix);
        return (
          <div className={classes.join(' ')} />

    Or in a more compact way:

    export default class Block extends Component {
      render() {
        return (
          <div className={`block ${this.props.visible ? 'block_visible' : ''} ${this.props.type ? `block_type_${this.props.type}` : ''} ${this.props.size ? `block_size_${this.props.size}` : 'block_size_m'} ${this.props.mix}`} />

    With usage like this:

    <Block visible={true} type="primary" size="xxl" mix="block2__elem"/>

    And it's totally fine, but it's exhausting and takes a lot of time.

    This helper was built to solve the problem described above. It's created around the convention that developer should pass BEM modifiers through mods property, and mixes throught mix. So, component invoking described above can be rewritten like this:

    <Block mods={{ visible: true, type: 'primary', size: 'xxl' }} mix="block2__elem"/>

    As you may understand, now it's quite easy to preprocess modifiers, change them, replace with default values, etc. And that's exactly what the helper does. When developer uses the helper, component code usually looks like this:

    import b from 'bem-react-helper';
    export default class Block extends Component {
      render() {
        return (
          <div className={b('block', this.props, { size: 'm' })} />

    As you see, there is no any conditions at all. What we have here is the function b with three arguments:

    • name — entitity name (block or element according to BEM naming); required;
    • props — props object (in most cases it's exactly props of React component, but it also can be built from stratch as an object with mods and mix keys, both are optional); default: {};
    • defaultMods — object with default values for modifiers; default: {}.

    That's all.

    Helper is a pretty smart guy. For example, you can pass mix as an array if you need to:

    <Block mods={{ visible: true, type: 'primary', size: 'xxl' }} mix={['block2__elem', 'block3']}/>

    Or you can use camelCased modifiers that will be converted to regular for CSS kebab-case. For example, let's assume that we use Block component described above, but with these modifiers:

    <Block mods={{ visible: true, type: 'primary', size: 'xxl', buttonSize: 'x' }} mix={['block2__elem', 'block3']}/>

    The helper will generate className value like this:

    block block_visible block_type_primary block_size_xxl block_button-size_x block2__elem block3

    Quite easy, huh?

    Also, if you want to use mods or mix inside the component inself, or pass other arguments, the best way to do that is:

    import b from 'bem-react-helper';
    export default class Block extends Component {
      render() {
        const { mix, mods = {}, } = this.props;
        return (
          <div className={b('block', this.props, { size: 's' })} {}>
              mods.type === 'primary' && (
                <span className="block__star"></span>

    And if you use build tools like webpack, you can use plugins like ProvidePlugin to get rid of import state in every component:

    // somewhere in a webpack config
    new webpack.ProvidePlugin({
      b: 'bem-react-helper',


    Why didn't I use all of the others helpers and created yet another one? I don't like the fact that they bloat my code and make all components strongly vendored to them. Also I believe that to write plain classes is faster than to use any wrappers around it.

    So this helper solves just one problem (the main) — it removes conditions for modifiers and mixes in block's declaration.


    npm i bem-react-helper

    DownloadsWeekly Downloads






    Unpacked Size

    9.62 kB

    Total Files


    Last publish


    • igoradamenko