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

API to return whether a selector has non-standard syntax.

Open
#135 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
web-dev

Research direction

The issue does not name files, tests, or entry points. Start by reviewing the parser's public API and existing syntax handling; done means strict parsing errors on non-standard syntax and non-strict parsing identifies offending nodes and selector parts.

Written by the indexing model from the issue text.

Description

enhancement
  1. add a strict parse mode so that any non-standard syntax is an immediate error.
  2. When not strict, it should be possible to find which nodes contain non standard syntax and for complex nodes like Attribute, which part(s) are violating the css spec.
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.