Support postcss-js parser
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- cli
Research direction
No file or test is named in the issue. Start by reading postcss-js/issues/23 and tracing the CLI's file-loading path; done means postcss-js parser input is supported without breaking normal file loading.
Written by the indexing model from the issue text.
Description
This requires special-casing to use require (or similar) for file loading, instead of the normal fs.
See https://github.com/postcss/postcss-js/issues/23 for details.
This will not be implemented before v3.0.0.
- Dominant language
- JavaScript
- Stars
- 857
- Forks
- 91
- Avg merge
- 7h 10m
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from postcss/postcss-cli
-
Dependency Dashboard Opendeps
Difficulty 1/5 Under an hour Newbie friendliness 10/100
postcss/postcss-cli#399 ·
All issues in postcss/postcss-cli
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·