OpenZeppelin / OpenZeppelin/compact-contracts
Create common dev dependencies config
Open
Nobody has claimed this yet.
2-low
beginner
effort: 2-S
enhancement
stale
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Many of our packages use the same dependencies such as biome, @types/node, typescript, etc. We should create a common config to use across our packages to keep them in sync in less error prone manner
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
Inspect the package manifests and existing dependency declarations across the repository to identify the shared development dependencies, including Biome, @types/node, and TypeScript. Determine how a common configuration can be consumed by the packages, then verify that the packages stay synchronized without duplicating version declarations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, developer-experience, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100