parseley - npm Package Compare versions

Comparing version 0.9.0 to 0.9.1

CHANGELOG.md

 # Changelog
 
+## Version 0.9.1
+
+* Fix namespace parsing;
+* Remove terser, use only `rollup-plugin-cleanup` to condition published files.
+
 ## Version 0.9.0
@@ -4,0 +9,0 @@

package.json

 {
   "name": "parseley",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "CSS selectors parser",
@@ -53,3 +53,3 @@ "keywords": [
     "leac": "^0.5.0",
-    "peberminta": "^0.5.2"
+    "peberminta": "^0.5.4"
   },
@@ -70,3 +70,3 @@ "devDependencies": {
     "rollup": "^2.60.2",
-    "rollup-plugin-terser": "^7.0.2",
+    "rollup-plugin-cleanup": "^3.2.1",
     "ts-node": "^10.4.0",
@@ -73,0 +73,0 @@ "tslib": "^2.3.1",

README.md

@@ -15,3 +15,3 @@ # parseley
 
-## Goals / features
+## Features
 
@@ -22,18 +22,10 @@ * Convert CSS selector strings into objects that are easy to work with;
 
-* Get specificity for free;
+* Get specificity for free.
 
-* Code is easy to understand and maintain.
 
+## Changelog
 
-## Non-goals
+Available here: [CHANGELOG.md](https://github.com/mxxii/parseley/blob/main/CHANGELOG.md).
 
-* Top performance;
 
-* Extra permissivity;
-
-* To-the-letter CSS spec implementation.
-
-These are great but only as long as it doesn't come in conflict with actual goals.
-
-
 ## Install
@@ -117,12 +109,2 @@
 
-## Motivation and inspiration
-
-| Package    | Hits      | Misses
-| ---------- | --------- | ---------
-| [parsel](https://github.com/leaverou/parsel) | Sensible AST; specificity calculation; cool name | Not friendly to node.js; based on regex
-| [css-what](https://github.com/fb55/css-what) and [css-select](https://github.com/fb55/css-select) | The idea to process complex selectors in right-to-left order | `css-select` is a solution for a different problem compared to what I needed; `css-what` produces only a list of tokens
-| [scalpel](https://github.com/gajus/scalpel)  | Introduced me to [nearley](https://nearley.js.org/) parsing toolkit (albeit I'm not using it here anymore) | AST it produces is very far from what I can use
-| [css-selector-parser](https://github.com/mdevils/css-selector-parser) | Configurable and lightweight | Again, AST is far from my needs
-
-
 ## Input reference
@@ -152,11 +134,9 @@
 
-## Changelog
+## Motivation and inspiration
 
-Available here: [CHANGELOG.md](https://github.com/mxxii/parseley/blob/main/CHANGELOG.md).
-
-
-## Roadmap
-
-* add pseudo-classes and pseudo-elements support ([#12](https://github.com/mxxii/parseley/issues/12))
-
-Share your use cases in [issues](https://github.com/mxxii/parseley/issues) so I can get a better idea where to move.
+| Package    | Hits      | Misses
+| ---------- | --------- | ---------
+| [parsel](https://github.com/leaverou/parsel) | Sensible AST; specificity calculation; cool name | Not friendly to node.js; based on regex
+| [css-what](https://github.com/fb55/css-what) and [css-select](https://github.com/fb55/css-select) | The idea to process complex selectors in right-to-left order | `css-select` is a solution for a different problem compared to what I needed; `css-what` produces only a list of tokens
+| [scalpel](https://github.com/gajus/scalpel)  | Introduced me to [nearley](https://nearley.js.org/) parsing toolkit (albeit I'm not using it here anymore) | AST it produces is very far from what I can use
+| [css-selector-parser](https://github.com/mdevils/css-selector-parser) | Configurable and lightweight | Again, AST is far from my needs

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Minified code

Quality

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

36515

increased by36.54%

Lines of code

715

increased by190.65%

Number of low quality alerts

1

decreased by-50%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Number of lines in readme file

139

decreased by-12.58%

Dependency changes

• Updatedpeberminta@^0.5.4