Linter
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
- developer-experience, tooling
Research direction
No files, tests, or entry points are named. Start by inventorying the JavaScript project's existing package scripts and commit workflow, then determine the required linter, Prettier, and Husky configuration. Done means the tools are configured and commit hooks prevent lint or formatting failures.
Written by the indexing model from the issue text.
Description
- Dominant language
- JavaScript
- Stars
- 206
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
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 didierfranc/react-code-splitting
-
Write tests Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Setup travis Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
didierfranc/react-code-splitting#20 · 1 comment ·
-
multi copy of react Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
didierfranc/react-code-splitting#15 · 1 reaction ·
All issues in didierfranc/react-code-splitting
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 ·