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

css-patch

v1.2.0

Published

CSS patch generator.

Downloads

14

Readme

css-patch

npm versionnode versionBuild status - Linux/OSXBuild status - WindowsCodecov

Generating CSS patches (just like a diff).

Use cases

Themes generation

The easiest way to make a new theme is to copy the file and change some stuff or, if you use a preprocessor (such as SCSS, Less, etc.), change some variables and get a new stylesheet.

But serving files with big amount of the same code is not a good idea, so this is when css-patch can help you.

You can pass 2 stylesheets (original/base and expected) to generateCSSPatch and get a new stylesheet. This new stylesheet is intended to be applied after original one and will have the same effect as if you applied expected one. In other words, the new stylesheet will consist of the resulting "overloads" for the original one.

Extracting difference

Imagine that you have two versions of the same CSS stylesheet.

By using this module you can get the difference between them.

Install

Install via yarn:

yarn add css-patch

Install via npm:

npm i css-patch

Docs

Read the docs on GitHub pages.

For advanced usage see the docs for transformCSS function and CSSTransformerBase class.

Possible caveats

unset

Declarations missing in expected stylesheet, but present in original one, will be set to unset.

Combined rule orders

Logically the same but with a different order combined rules (e.g..a,.b and .b,.a) will be considered as a different rules.

Merged rules

Rules with the same name will have their declarations merged with each other, overriding previous declarations in the order they appear.

For example .a{a:1;c:3;}.a{a:2;b:2;} will be treated as .a{a:2;b:2;c;3}.

Sorting

Declarations are sorted alphabetically.

Usage example

Import

CommonJS

const { generateCSSPatch, } = require('css-patch');

ES6

import { generateCSSPatch, } from 'css-patch';

Use

console.log(
	generateCSSPatch(`
a { same: value; missing: value; }
b { different: original_value; }
c { same: rule; }
missing_rule { missing: value; }
		`, `
a { same: value; }
b { different: new_value; }
c { same: rule; }
		`
	)
); // 'a{missing:unset;}b{different:new_value;}missing_rule{missing:unset;}'