postcss-selector-parser
postcss-selector-parser copied to clipboard
A CSS selector parser, integrates with postcss but does not require it.
```js require('postcss-selector-parser')(node => console.dir(node.nodes[0].nodes[0].attribute)).processSync('[#{$b}]') // '#{b}' ``` `#{$b}` is expected.
I could see there's a fork of the abandoned coveralls package. Are you guys considering a replacement with a fork of it like [coveralls-next](https://www.npmjs.com/package/coveralls-next) or there's another plan?
related to https://github.com/postcss/postcss-nested/issues/169
When using the [`loseless: true`](https://github.com/postcss/postcss-selector-parser/blob/6158750aab0aed3046a5920bd58e0e0266a4ada2/API.md#processoroptions) option trailing spaces are removed unexpectedly, even though should be preserved. Related to https://github.com/stylelint/stylelint/pull/8074#discussion_r1817680694 ## Code to Reproduce ```js const parser = require('postcss-selector-parser'); const selector...
Bumps [form-data](https://github.com/form-data/form-data) to 4.0.4 and updates ancestor dependency [coveralls-next](https://github.com/jtwebman/coveralls-next). These dependencies need to be updated together. Updates `form-data` from 4.0.0 to 4.0.4 Release notes Sourced from form-data's releases. v4.0.4 v4.0.4...
Bumps [js-yaml](https://github.com/nodeca/js-yaml) to 3.14.2 and updates ancestor dependencies [js-yaml](https://github.com/nodeca/js-yaml) and [coveralls-next](https://github.com/jtwebman/coveralls-next). These dependencies need to be updated together. Updates `js-yaml` from 3.14.1 to 3.14.2 Changelog Sourced from js-yaml's changelog. [3.14.2]...
According to the CSS Selectors Level 4 specification, the [Case-sensitivity](https://www.w3.org/TR/selectors-4/#attribute-case) identifiers are `i` and `s`. However, it seems that `postcss-selector-parser`(v7.1.0) does not support `s`. ```typescript import parser from 'postcss-selector-parser'; const...