feat: add support for class prefix selectors (.foo-*)

[Copilot]

Adds parsing support for CSS class prefix selectors per w3c/csswg-drafts#10001. A selector like .foo-* now produces a single class AST node rather than being split into a class and universal selector.

• Parser (src/parser.js): In splitWord(), when a word contains a class dot and ends with -, consume the following * token into the word. This produces a single ClassName node with the wildcard suffix.
• Tests (src/__tests__/classes.mjs): Added cases for .foo-*, div.foo-*, and .foo-*.bar-*.

const parser = require('postcss-selector-parser');
const result = parser().astSync('.foo-*');

result.nodes[0].nodes[0].type;  // "class"
result.nodes[0].nodes[0].value; // "foo-*"
result.toString();              // ".foo-*"

Note: div-* (no class dot) still correctly produces tag + universal selector — the prefix logic only fires when a . class indicator is present in the word.

• Fixes [tentative] Add support for .foo-* class prefix selectors #332

[MoOx]

@romainmenke any feedback for this?

[Copilot]

Pull request overview

Adds parsing support for CSS “class prefix selectors” of the form .foo-*, intending to treat them as a single class node (value foo-*) instead of splitting into class + universal.

Changes:

• Update splitWord() to optionally consume a trailing * token into a class-like word ending in -.
• Add new test cases covering .foo-*, div.foo-*, and .foo-*.bar-*.
• Bump the lockfile version metadata (package-lock.json) to 7.1.5.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/parser.js	Extends splitWord() to fold * into .foo- words and adjust token reference used for source calculations.
src/tests/classes.mjs	Adds new class-prefix selector parsing assertions.
package-lock.json	Updates package version fields to 7.1.5.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[romainmenke]

I choose not to spend time reading or reviewing LLM generated content.
Happy to answer any questions or review code written by a person.
Hope you understand :)

[MoOx]

Sure no problem.