Abstract code standards (eslint, &c) to a shared org-wide package
Open
Nobody has claimed this yet.
improvement
refactor
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
- linter, eslint, prettier, vscode
- we should publish a package with shared standards
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.
Research direction
Start by locating the repository's linter, ESLint, Prettier, and VS Code configuration, then determine which standards belong in a shared package. Done means the shared standards package is defined and published for org-wide use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript, vscode
- Domain
- build-system, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100