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

add-bem-name

v1.0.0

Published

Util to create class names with BEM methodology

Downloads

1

Readme

Motivation

This util was made to make development with BEM-methodology easier. It abstracts the component structure from its block name and adds a list of benefits, such as:

  • Make components more readable.
  • Make refactoring easier. Block name declared on the top of the file and abstracted from component's structure. You don't need to edit the render method if you changed the component name.
  • There's less space for mistypes and related bugs.
  • Different blocks couldn't affect each other. The error will be raised if you try to use the same block name twice.
  • The js bundle will be lighter.

Before:

import classnames from 'classnames'

const AwesomeElement = ({ active }) => (
  <div className="long-name-of-the-element">
    <h1 className={classnames(
      'long-name-of-the-element__heading', {
      "long-name-of-the-element__heading--active": active,
    })}>
    <ul className="long-name-of-the-element__content">
      <li className="long-name-of-the-element__item" />
      <li className="long-name-of-the-element__item" />
      <li className="long-name-of-the-element__item" />
    </ul>
  </div>
);

After:

import addBemName from 'bem-name';
import classnames from 'classnames'

const bemName = addBemName('long-name-of-the-element');

const AwesomeElement = ({ active }) => (
  <div className={bemName()}>
    <h1 className={classnames(
      bemName('heading'), { [bemName('heading', 'active')]: active }
    )} >
    <ul className={bemName('content')}>
      <li className={bemName('item')} />
      <li className={bemName('item')} />
      <li className={bemName('item')} />
    </ul>
  </div>
);

How to use it

At first you register a block name:

const bemName = addBemName('block-name');

This function takes a string with block name and returns a function you can use in four different ways:

  • bemName() returns a block (or component in BEM-methodology) name
  • bemName('element-name') returns a element name like 'block-name__element-name'
  • bemName('element-name', 'active') returns a element name with modificator: 'block-name__element-name--active'
  • bemName(null, 'active') returns a block name with modificator: 'block-name--active'

Use modificators

As you could see above, Each function call returns only one specified class. You can easily combine modificators with classnames util:

classnames(bemName('item'), {
  [bemName('item', active)]: active,
  [bemName('item', red)]: red,
});

Tests

This util is covered with tests. You can run it with yarn test