OpenZeppelin / OpenZeppelin/compact-contracts
Update Yarn Berry configs to use native PlugNPlay
Open
Nobody has claimed this yet.
enhancement
stale
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Our configuration is using the node_modules nodeLinker option. We should look into whether using the recommended "pnp", option is feasible to take full advantage of Yarn Berry
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
The issue does not name a configuration file or test. Locate the Yarn Berry configuration and inspect the current nodeLinker setting first; compare the repository's existing install and build workflow with Plug'n'Play, and consider the work done when that workflow succeeds with the recommended pnp setting.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100