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

@haaretz/sass-selectors

v1.0.2

Published

Helpers for manipulating selectors in Sass

Downloads

8

Readme

@haaretz/sass-selectors

Helpers for manipulating selectors in Sass

Haaretz interactive element are often used in a quote-unquote, "hostile environment", included into pages that are already ripe with global styles.

Therefore, they should be both robust - as unlikely as possible to be affected by preexisting styles - and unobtrusive - styled in a manner that ensures they will not affect already existing styles.

This module exposes mixins and functions designed for this purpose - allowing for the creation and use of prefixed css-custom-properties and BEM-style selectors.

Installation

yarn add --dev @haaretz/css-selectors

or with npm:

yarn install --save-dev @haaretz/css-selectors

Usage

@import '~@haaretz/css-selectors'

Configuration

@haaretz/sass-selectors exposes the following configuration variables:

$selector-prefix

The prefix added to classes and custom properties
type: string
default: ''

$element-separator

The separator used for BEM child elements
type: string
default: '__'

$modifier-separator

The separator used for BEM modifiers
type: string
default: '--'

$state-prefix

The default prefix for state classes
type: string
default: 'is'

$qualify-state

Should state classes be added as qualifiers like in SMACSS (e.g., .base-class.is-state) this increasing specificity or as a single class like in classic BEM (e.g. .base-class--is-state) thus retaining flatters specificity.
type: boolean
default: true

Custom Property Helpers

create-var

Create custom properties that are prefixed to avoid name collusion but without the syntactic verbosity of repeatedly doing: --#{$selector-prefix}variable-name: variable-value;
Type: mixin
Params:
$name (string): The custom-property's unprefixed name
$value (any): The value assigned to the custom-property
Example:

.foo {
  @include create-var(primary, red);
}
// Assuming `$selector-prefix: bar-`, will generate:
// .foo { --bar-primary: red; }

use-var

Use a prefixed custom properties to avoid name collusion but without the syntactic verbosity of repeatedly doing: color: var(--#{$selector-prefix}color1);
Type: function
Params:
$name ('string'): The unprefixed name of the variable to use. Usually one defined using the css-var mixin.
Return: (string) Prefixed custom property usage
Example:

.foo {
  color: use-var(primary);
}
// Assuming `$selector-prefix: bar-`, will generate:
// .foo { color: var(--bar-primary); }

BEM Helpers

class

Create class selectors that are prefixed to avoid name collusion but without the syntactic verbosity of repeatedly doing: .#{$selector-prefix}name { ... }.

Can be used to create any class, but designed chiefly to be used as an idiomatic way to create BEM block rulesets (hense, aliased as b)
Alias: b
Type: mixin
Params:
$names (arglist): Unprefixed class name(s) to create the selector from
Examples:

// Single class:
@include class(foo) { color: red; }
// Assuming `$selector-prefix: bar-`, will generate:
// .bar-foo { color: red; }

// Multiple class:
@include class(foo, bar) { color: red; }
// Assuming `$selector-prefix: bar-`, will generate:
// .bar-foo, .bar-bar { color: red; }

// Scoped:
.scope { @include class(foo) { color: red; } }
// Assuming `$selector-prefix: bar-`, will generate:
// .scope {.bar-foo { color: red; } }

element

Idiomatically create BEM element rulesets. Can be nested inside modifiers or other elements to infinite depth.
Alias: e
Type: mixin
Params: $name (string): The element's name
Example:

@include b(foo) {
  ...
  @include element(bar) { ... } // -> .foo__bar { ... }
}

modifier

Idiomatically create BEM modifier rulesets. Can be nested inside elements or other modifiers to infinite depth
Alias: m
Type: mixin
Params:
$name (string): The modifier's name
Example:

@include b(foo) {
  ...
  @include modifier(bar) { ... } // -> .foo--bar { ... }
}

is

Idiomatically create state qualifier classes of a parent selector
Alias: state
Type: mixin
Params:
$state (string): The represented state
$prefix (string): The string to use when prefixing $state, e.g, @include is(open, is) { ... } will create an .is-open qualifier. default: $state-prfix.
$qualify (boolean): Should state classes be added as qualifiers like in SMACSS (e.g., .base-class.is-state) thus increasing specificity or as a single class like in classic BEM (e.g. .base-class--is-state) thus retaining flatter specificity.
Example:

html {
  ...
  @include is(app) { ... } // -> .html.is-app { ... }
}

Qualifiers

when-is

Qualify a selector with another selector to increase specificity
Alias: qualify
Type: mixin
Params:
$qualifier (string)
Examples:

// Qualify element with a class:
button {
  @include when-is(.large) { ... } // -> button.large {...}
}

// Qualify class when a certain element:
.button {
  @include when-is(a) { ... } // -> a.button {...}
}