logzio / logzio/yarn-one-version-rule
Yarn v2/3 and ignoring dependency of dependency
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
- This does not work with yarn v2 and 3.
(This is easily fixable)
- This also ignores dependency of dependency and dependency of dependency of dependency...
Is this by design?
Contributor guide
No contributing guide indexed for this repository
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 reproducing the reported behavior with Yarn v2 and v3, including dependencies several levels deep, and inspect how the rule discovers workspace dependencies. Done means the intended handling of Yarn v2/3 and transitive dependencies is established and covered by tests, including whether recursive ignoring is by design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100