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

@troglotit/bem-sass-mixins

v1.0.0

Published

Minimalistic core. Supports mixins: +m(<list of modifiers>) and +e(<list of elements>) with nest-in-state support.

Downloads

3

Readme

Bem class mixins

Minimalistic core. Supports mixins: +m(<list of modifiers>) and +e(<list of elements>) with nest-in-state support.

Usage

Install

npm i -S bem-sass-mixins

Include

Webpack

@import '~bem-sass-mixins/bem-sass-mixins' (Sass 4.0 will give us improved resolving)

Gulp

See gulp-sass options. You'll need includePaths option to resolve @import 'bem-sass-mixins' (from node_modules/bemsass-mixins) or @import 'bem-sass-mixins/bem-sass-mixins' (from node_modules/). Looks simple enough to configure.

Configure

Define preferrable separators in your variables file like $bemSeparators: (element: '-', modifier: '--') (these are mine for .MyBlock-myElement--myModifier style) or rely on defaults __ and --.

Use

I came to conclusion that it was ALWAYS better to write blocks as pure classes. Problems happen when composing mixins which represent blocks. E.g. we cannot have two block mixins each under another, so we may think about list of blocks passed to mixin. Ok, but what if we also want to specify namespaces, which may also be different per block or even absent for some blocks?

Nevermind... Looks like unnecessary work at all.

.Block
  color: red
  +e(element1 element2)
    color: green
    +m(elementModifier1 elementModifier2)
      color: blue
  +m(blockModifier1 blockModifier2)
    color: red
    +e(element)
      color: green
      +m(elementModifier)
        @extend %TestPlaceholder // Stylus can't do this without ugly prefix :)
        color: blue

Will produce:

.Block {
  color: red;
}
.Block-element1, .Block-element2 {
  color: green;
}
.Block-element1--elementModifier1, .Block-element1--elementModifier2, .Block-element2--elementModifier1, .Block-element2--elementModifier2 {
  color: blue;
}
.Block--blockModifier1, .Block--blockModifier2 {
  color: red;
}
.Block--blockModifier1 .Block-element, .Block--blockModifier2 .Block-element {
  color: green;
}
.Block--blockModifier1 .Block-element--elementModifier, .Block--blockModifier2 .Block-element--elementModifier {
  color: blue;
}

.Block--blockModifier1 .Block-element--elementModifier, .Block--blockModifier2 .Block-element--elementModifier {
  font-weight: bold;
}