Only one eslintrc
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 280
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
We currently have an eslintrc for each package, but we want a consistent style in the repo. Instead of copying it everywhere, we should have just one.
Contributor guide
Research direction
Locate the eslintrc files in each package and compare their contents to identify the shared configuration. Consolidate the configuration at the repository level, update package references as needed, and run the repository's lint checks to confirm all packages use the single configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100