madyankin / madyankin/postcss-modules

Support "Pure" scope as in CSS-loader

Open
#106 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.6k
Forks
88
PR merge metrics
No merged PRs in 30d

Description

As titled. https://github.com/webpack-contrib/css-loader#scope

This would allow to have real "No global scope." for CSS modules.

Example:

Syntax error: Selector ":global .page" is not pure (pure selectors must contain at least one local class or id)

  17 |   pointer-events: none;
  18 | }
> 19 | :global .page {
     |                                             ^
  20 |   width: 4px;
  21 | }

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.

Research direction

Start by reading the CSS Modules scope handling and compare the requested behavior with the linked CSS-loader scope documentation. The work is done when a Pure scope is supported and selectors such as :global .page are accepted while enforcing the stated requirement that pure selectors contain a local class or id.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.