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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lime-soda/cem-plugin-css-properties

v0.3.0

Published

Custom Elements Manifest plugin for adding CSS custom properties from design tokens

Readme

@lime-soda/cem-plugin-css-properties

A Custom Elements Manifest (CEM) plugin that automatically adds CSS custom properties from design tokens to your custom element manifests.

Installation

npm install @lime-soda/cem-plugin-css-properties

Usage

Basic Usage with Element Prefix

import { cssPropertiesPlugin } from '@lime-soda/cem-plugin-css-properties'
import tokens from './design-tokens.js'

export default {
  plugins: [
    cssPropertiesPlugin(tokens, {
      prefix: 'ls', // Removes 'ls-' prefix from element names (dash added automatically)
    }),
  ],
}

Advanced Usage with Custom Mapping Function

import { cssPropertiesPlugin } from '@lime-soda/cem-plugin-css-properties'
import tokens from './design-tokens.js'

// Custom mapping function
function mapElementToTokens(manifest, tokens) {
  const mapping = new Map()

  // Process manifest to create custom mappings
  if (manifest.modules) {
    for (const module of manifest.modules) {
      if (module.declarations) {
        for (const declaration of module.declarations) {
          if (declaration.tagName) {
            // Custom logic for mapping element to token key
            const baseName = declaration.tagName.replace(/^ls-/, '')

            switch (baseName) {
              case 'btn':
                mapping.set(declaration.tagName, 'button')
                break
              case 'input-field':
                mapping.set(declaration.tagName, 'input')
                break
              default:
                if (baseName in tokens) {
                  mapping.set(declaration.tagName, baseName)
                }
            }
          }
        }
      }
    }
  }

  return mapping
}

export default {
  plugins: [
    cssPropertiesPlugin(tokens, {
      mapElementToTokens,
    }),
  ],
}

Configuration

PluginOptions

| Option | Type | Default | Description | | -------------------- | ----------------------------------------------------------------------------- | ------- | ----------------------------------------------------------------------- | | mapElementToTokens | (manifest: Package, tokens: Record<string, unknown>) => Map<string, string> | - | Custom function to map elements to token keys | | prefix | string | 'ls' | Element prefix to remove for default mapping (dash added automatically) |

Debug Output

The plugin uses the debug package for conditional logging. Set the DEBUG environment variable to control output:

# Show all plugin debug output
DEBUG=cem-plugin:* npm run build-manifest

# Show only main plugin operations
DEBUG=cem-plugin:css-properties npm run build-manifest

# Show only element-to-token mapping debug info
DEBUG=cem-plugin:css-properties:mapping npm run build-manifest

# Show only token extraction debug info
DEBUG=cem-plugin:css-properties:extraction npm run build-manifest

# Combine multiple namespaces
DEBUG=cem-plugin:css-properties:mapping,cem-plugin:css-properties:extraction npm run build-manifest

Debug Namespaces

  • cem-plugin:css-properties - Main plugin operations (element processing, property addition)
  • cem-plugin:css-properties:mapping - Element-to-token mapping creation and statistics
  • cem-plugin:css-properties:extraction - Token extraction processes and results

Token Structure

The plugin expects design tokens to follow this structure:

const tokens = {
  button: {
    primary: {
      background: {
        $value: '#4ade80',
        $type: 'color',
        $description: 'Primary button background',
        name: 'button-primary-background',
      },
    },
  },
}

Output

The plugin adds CSS custom properties to your Custom Elements Manifest:

{
  "cssProperties": [
    {
      "name": "--button-primary-background",
      "description": "Primary button background",
      "default": "#4ade80"
    }
  ]
}

License

MIT