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

@spectrum-tools/postcss-add-theming-layer

v0.0.0

Published

Leveraging style container queries to create an abstraction layer for supporting multiple theming systems

Downloads

7

Readme

postcss-add-theming-layer

Leveraging style container queries to create an abstraction layer for supporting multiple theming systems.

Installation

Add the dependency to your project:

npm install postcss-add-theming-layer

or

yarn add -DW postcss-add-theming-layer

Use the plugin in your PostCSS configuration:

module.exports = {
  plugins: {
    "postcss-add-theming-layer": {},
  },
};

or as part of your CLI command:

postcss -u postcss-add-theming-layer -o dist/index.css src/index.css

Options

selectorPrefix [string]

This optional input will prefix the new theming layer selector with the provided string. This can be useful if you want to namespace the injected selectors for the new theming layer to avoid conflicts.

skipMapping [boolean=false]

Skip the mapping of the variables to the system variables. This can be useful if you only want to extract the variables and not map them to the system variables.

preserveVariables [boolean=true]

When used with skipMapping, this option will preserve the variables defined inside the container query in the output by injecting them to the root selector.

referencesOnly [boolean=false]

This option will only output those variables that are referencing the newly created system variables and not the system variables themselves. This can be used as a bridge between an old and new implementation for the component.

stripLocalSelectors [boolean=false]

This option will remove the local selectors (those that map to system variables) from the output leaving only the system definitions.

processIdentifier [(identifierValue: string, identifierName: string) => string]`

Customize the selectors that variables are placed in. Passed the value and key of the variable that was passed to the container, i.e. identifierValue = spectrum and identifierName = system for the example below. By default, identifierName is used as-is.

Usage

This plugin turns this:

@container style(--system: legacy) {
  .component {
    --background-color: blue;
  }
  .component.is-selected {
    --background-color: darkblue;
  }
  .component .icon {
    --color: gray;
  }
}

@container style(--system: modern) {
  .component {
    --background-color: purple;
  }
  .component.is-selected {
    --background-color: darkpurple;
  }
  .component .icon {
    --color: white;
  }
}

Into this:

.legacy {
  --system-component-background-color: blue;
  --system-component-selected-background-color: darkblue;
}

.modern {
  --system-component-background-color: purple;
  --system-component-selected-background-color: darkpurple;
}

.component {
  --background-color: var(--system-component-background-color);
}

.component.is-selected {
  --background-color: var(--system-component-selected-background-color);
}

Usage notes

This plugin will ignore any underscore-prefixed variables, as they are considered private and not part of the theming layer.