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

@sardine/lightningcss-plugin-source

v1.0.0

Published

A shared CSS source parser for Lightning CSS plugins

Readme

@sardine/lightningcss-plugin-source

Parse one CSS source file once and share its indexed values across Lightning CSS plugins. This avoids repeated filesystem reads and parsing when several plugins use the same tokens file.

  • One parse. createCssSource() reads and bundles the source immediately.
  • Shared indexes. Custom properties and @custom-media definitions are available from one handle.
  • Explicit lifetime. The caller owns the handle, so there is no process-global cache or hidden invalidation behavior.
const source = createCssSource("./src/tokens.css");

composeVisitors([
	globalCustomQueries({ source }),
	customPropertyFallback({ source }),
]);

Installation

npm install --save-dev @sardine/lightningcss-plugin-source

Install the Lightning CSS plugins that will consume the source handle separately.

Usage

import { createCssSource } from "@sardine/lightningcss-plugin-source";
import customPropertyFallback from "@sardine/lightningcss-plugin-custom-property-fallback";
import globalCustomQueries from "@sardine/lightningcss-plugin-global-custom-queries";
import { composeVisitors, transform } from "lightningcss";

const source = createCssSource("./src/tokens.css");

const { code } = transform({
	filename: "component.css",
	code: Buffer.from(`
		@media (--narrow) {
			.card { margin: var(--space-md); }
		}
	`),
	visitor: composeVisitors([
		globalCustomQueries({ source }),
		customPropertyFallback({ source }),
	]),
});

API

createCssSource(filename)

Reads and parses filename, then returns a CssSource containing read-only indexes:

  • customMedia: custom media names mapped to their parsed conditions.
  • customProperties: custom property names mapped to their parsed token values.
  • filename: the source path used to create the handle.

Custom properties are indexed in source order. When a property appears more than once, the last declaration wins.

resolveCssSource(source)

Returns an existing CssSource unchanged or creates one when given a string path. Plugin authors can use this helper when accepting CssSourceInput directly.

The handle is a snapshot. Create a new handle when the source file changes.