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

@pobedit/kefir

v1.0.0

Published

A BEM friendly class name generator

Downloads

9

Readme

@pobedit/kefir

Build Status License

A BEM friendly class name generator.

Installation

Install with npm or Yarn:

npm:

npm install @pobedit/kefir --save

Yarn:

yarn add @pobedit/kefir

Basic usage

We have a wide variety of semantically correct BEM rules:

import {$} from '@pobedit/kefir';

$('foo', 'bar');
// foo__bar

$('foo', {bar: true});
// foo foo--bar

$('foo', 'bar', {baz: true});
 // foo__bar foo__bar--baz

$('foo', {bar: true}, ['baz']);
 // foo foo--bar baz

$('foo', ['bar']);
 // foo bar

$('foo', 'bar', ['baz', 'gaz']);
 // foo__bar baz gaz

$('foo', 'bar', {baz: true}, ['taz']);
 // foo__bar foo__bar--baz taz

React usage

import React, {ReactNode, useState} from 'react';
import {$} from '@pobedit/kefir';

type Props = {
   bar: boolean
}

export const Example: React.FunctionComponent<Props> = (props) => {
   const {bar} = props;

   return (
       <div className={$('foo', 'container', {bar})}>
           <button className={$('button', { baz })}>
               Click!
           </button>
       </div>
   );
};

Output:

<div class="foo__container foo__container--bar">
    <button class="button button--baz">Click</button>>
</div>

So, your CSS structure looks like:

.foo {
  &__container {
      &--bar {
        background-color: red;
      }
  }
}

.button {
  &--baz {
    color: white;
  }
}

API

Parameters

| Name | Type | Description | |-------------|----------|-----------------------------------------------------------------| | block | string | Encapsulates a standalone entity that is meaningful on its own. | | element | string | Parts of a block and have no standalone meaning. | | modifiers | object | Flags on blocks or elements. | | extra | string[] | A set of additional classes. |

$

$ is a highly polymorphic function with the following interfaces:

Block

import {$} from '@pobedit/kefir';

$('foo');
 // foo

Element

import {$} from '@pobedit/kefir';

$('foo', 'bar');
 // foo__bar

$('foo', 'bar', ['baz', 'gaz']);
 // foo__bar baz gaz

$('foo', 'bar', {baz: true});
 // foo__bar foo__bar--baz

$('foo', 'bar', {baz: true, gaz: true}, ['taz']);
 // foo__bar foo__bar--baz foo__bar--gaz taz

Modifier

import {$} from '@pobedit/kefir';

$('foo', {bar: true});
 // foo foo--bar

$('foo', {bar: true, gaz: true}, ['baz']);
 // foo foo--bar foo--gar baz

$('foo', ['bar']);
 // foo bar

API

Kefir

It's just a wrapper around the main function $:

import {$} from '@pobedit/kefir';

let $ = kefir('foo');

$({bar: true});
 // foo foo--bar

The second example of advanced usage:

import React, {ReactNode, useState} from 'react';
import {kefir} from '@pobedit/kefir';

type Props = {
   bar: boolean;
   baz: boolean;
}

export const Example: React.FunctionComponent<Props> = (props) => {
   const {bar, baz} = props;
   let $ = kefir('foo');

   return (
       <div className={$('container', { bar })}>
           <button className={$('button', { baz })}>
               Click!
           </button>
       </div>
   );
};

Output:

<div class="foo__container foo__container--bar">
    <button class="button button--baz">Click</button>>
</div>

Contributing

Feel free to submit a pull request if you find any bugs. Please make sure all commits are properly documented.

Tests

npm test

Publishing

npm publish --access public --verbose

License

MIT