feat: 1.2.0

Author: Zekfad

.appveyor.yml

@@ -1,12 +1,12 @@
 environment:
   matrix:
-    - nodejs_version: "10"
-    - nodejs_version: "11"
+    # - nodejs_version: "10"
+    # - nodejs_version: "11"
     - nodejs_version: "12"
     - nodejs_version: "13"
     - nodejs_version: "14"
     - nodejs_version: "15"
-    # - nodejs_version: "16"
+    - nodejs_version: "16"
 
 platform:
   - x64

.travis.yml

@@ -1,14 +1,16 @@
 language: node_js
 os: linux
 dist: xenial
+install: yarn install --frozen-lockfile --ignore-engines
 before_script: yarn build
 jobs:
   include:
-  - name: Node 10
-    node_js: 10
-  - name: Node 11
-    node_js: 11
-    install: yarn install --frozen-lockfile --ignore-engines
+  # - name: Node 10
+  #   node_js: 10
+  #   before_script: yarn build:src
+  # - name: Node 11
+  #   node_js: 11
+  #   before_script: yarn build:src
   - name: Node 12
     node_js: 12
   - name: Node 13
@@ -17,13 +19,14 @@ jobs:
     node_js: 14
   - name: Node 15
     node_js: 15
-  # - name: Node 16
-  #   node_js: 16
-#  - name: Latest Node - Windows
-#    node_js: node
-#    os: windows
+  - name: Node 16
+    node_js: 16
+  # - name: Latest Node - Windows
+  #   node_js: node
+  #   os: windows
   - name: Latest Node - OSX
     node_js: node
+    before_install: npm install -g yarn
     os: osx
   - name: Latest Node - Linux
     node_js: node

LICENSE

@@ -1,4 +1,4 @@
-Copyright 2020 Yaroslav Vorobev and contributors. All rights reserved.
+Copyright 2020-2022 Yaroslav Vorobev and contributors. All rights reserved.
 
 Permission to use, copy, modify, and/or distribute this software for any
 purpose with or without fee is hereby granted, provided that the above

ReadMe.md

@@ -5,16 +5,16 @@
 
 Generating CSS patches (just like a diff).
 
-## Reasons to use
+## Use cases
 
 ### Themes generation
 
-The easiest way to make a new theme is just copy the file and change some stuff
-or if you use preprocessor (such as SCSS, Less, etc.) you can just change some
-variables and get a new style.
+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 literally the same code is not a good idea,
-so this is when css-patch can help you.
+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
@@ -24,9 +24,9 @@ the `original` one.
 
 ### Extracting difference
 
-Imagine if you have two versions of the same CSS.
+Imagine that you have two versions of the same CSS stylesheet.
 
-You can use this module to get the "difference" between them.
+By using this module you can get the difference between them.
 
 ## Install
 
@@ -46,26 +46,26 @@ npm i css-patch
 
 [Read the docs on GitHub pages.](https://zekfad.github.io/css-patch/)
 
-For advanced usage see the docs for [`transformCSS`](https://zekfad.github.io/css-patch/global.html#transformCSS) function and [`CSSTransformerBase`](https://zekfad.github.io/css-patch/CSSTransformerBase.html) class.
+For advanced usage see the docs for [`transformCSS`](https://zekfad.github.io/css-patch/global.html#transformCSS) function and [`CSSTransformerBase`](https://zekfad.github.io/css-patch/CSSTransformers.CSSTransformerBase.html) class.
 
 ## Possible caveats
 
-###  `unset`
+### `unset`
 
-If something existed in `original` stylesheet missing in `expected` one, 
-will result of being transformed to `<something>: 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`)
+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
 
-If rules have exact the same name their declarations would be merged (later appeared
-declarations will be a higher priority).
+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 threat as `.a{a:2;b:2;c;3}`.
+For example `.a{a:1;c:3;}.a{a:2;b:2;}` will be treated as `.a{a:2;b:2;c;3}`.
 
 ### Sorting
 
@@ -91,9 +91,16 @@ import { generateCSSPatch, } from 'css-patch';
 
 ```js
 console.log(
-	generateCSSPatch(
-		'a{a:1;b:1;}b{b:1;}c{a:1;}d{a:1;}',
-		'a{a:1;}b{b:2;}c{a:1;}'
+	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{b:unset;}b{b:2;}d{a:unset;}'
+); // 'a{missing:unset;}b{different:new_value;}missing_rule{missing:unset;}'
 ```