Using @csstools/css-tokenizer

Open
#338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript
Domain
tooling

Research direction

Start in the postcss-selector-parser repository and compare its selector parsing responsibilities with the @csstools/css-tokenizer package. Determine whether the tokenizer is intended to cover selectors and what integration scope would be appropriate; the issue is complete only once that scope is agreed and an implementation path is defined.

Written by the indexing model from the issue text.

Description

Hello, since the same contributors seem to work on both packages, could postcss-selector-parser use the @csstools/css-tokenizer ? Or is it not in scope for the csstools tokenizer to cover selectors?

Dominant language
JavaScript
Stars
214
Forks
63
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from postcss/postcss-selector-parser

All issues in postcss/postcss-selector-parser

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.