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

@csstools/postcss-extract

v4.0.1

Published

Extract bits of your CSS

Downloads

1,334

Readme

PostCSS Extract

npm install @csstools/postcss-extract --save-dev

PostCSS Extract lets you easily export parts of your CSS source files to JavaScript objects.

your query :

rule[selector*=":root" i] > decl[variable]

your config :

postcssExtract({
	queries: {
		'your-export': 'rule[selector*=":root" i] > decl[variable]'
	},
	results: function(results) {
		console.log(results)
	}
})

your css :

:root {
	--your-property: cyan;
}

.other {
	--other-property: yellow;
}

the exported data :

[
	{ type: 'decl', prop: '--your-property', value: 'cyan', variable: true },
]

Usage

Add PostCSS Extract to your project:

npm install postcss @csstools/postcss-extract --save-dev

Use it as a PostCSS plugin:

const postcss = require('postcss');
const postcssExtract = require('@csstools/postcss-extract');

postcss([
	postcssExtract(/* pluginOptions */)
]).process(YOUR_CSS /*, processOptions */);

Options

queries

The queries option let's you define which parts of your CSS are exported. Each query is written in CSS.

Supported combinators:

  • > direct child
  • any descendant (space)
  • + adjacent sibling
  • ~ general sibling

Supported selectors:

  • * any node
  • atrule
  • rule
  • decl
  • comment
  • [type=decl]
  • [value=cyan]
  • [value=cyan i] case insensitive
  • [value^=cy] starts with
  • [value*=ya] contains
  • [value$=an] ends with
  • :not(<complex selector>)

Browse the PostCSS API to gain more insights into the AST naming and structure.

postcssExtract({
	queries: {
		'your-export': 'rule[selector*=":root" i] > decl[variable]'
	},
})

results

The results option let's you define a callback to receive results. You can then apply further transforms on the data so that it fits your use case.

postcssExtract({
	results: (yourResults) => {
		console.log(yourResults);
	},
})

extractLate

The extractLate option let's you define if the queries are run early or late in the PostCSS process.

extractLate: false uses Once in PostCSS. This means that it will try to run early.

extractLate: true uses OnceExit in PostCSS. This means that it will try to run late.

The order of plugins is still respected if multiple plugins use Once|OnceExit.