Mention supported browsers in doc, also promote browserslistrc
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
The issue has no body or named files. Start by locating the project documentation and any existing browserslistrc references, then document supported browsers and promote browserslistrc; done means both points are covered in the relevant documentation.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- JavaScript
- Stars
- 29.4k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 elsewhencode/project-guidelines
-
AQUAEDGE PROMOTIONS Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
elsewhencode/project-guidelines#176 · 1 comment ·
-
improvement
elsewhencode/project-guidelines#160 · 3 reactions · 1 assignee ·
-
improvement
elsewhencode/project-guidelines#140 · 1 assignee ·
-
improvement question
elsewhencode/project-guidelines#134 · 1 assignee ·
-
help wanted improvement
elsewhencode/project-guidelines#124 · 2 comments · 6 reactions · 1 assignee ·
All issues in elsewhencode/project-guidelines
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·