Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

invalid/non stable ast for combinator with comment

Open
#189 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
tooling

Research direction

Start by reproducing the two selector inputs from the issue and inspecting how comments are represented in the generated AST. Review the existing discussion and compatibility with stylelint and prettier; the work is done when equivalent comment placement produces a stable, analyzable AST without an unresolved compatibility decision.

Written by the indexing model from the issue text.

Description

bug

Input:

h2 /*test*/ h4 { } /* Here we don't have `comment` node in ast (store comment in `raws`) */
h2/*test*/h4 { } /* Comment in ast */

It is do impossible analyzes comments, also adopt new version to stylelint and prettier. For me it is bug, but fixing this change ast.

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.