OpenZeppelin / OpenZeppelin/compact-contracts
Create Common Config For tsconfig using Turbo best practices
Open
Nobody has claimed this yet.
stale
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Reference to relevant turbo docs
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
Read the linked Turborepo guide on sharing tsconfig.json, then inspect the repository's existing TypeScript configuration files and package layout. Done means a common configuration follows the documented best practices and the relevant projects use it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100