All dependencies moved to catalog instead of shared ones
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The readme states:
If there are more than 2 packages with same dependency - it will move dependency to catalog.
This doesn't seem to be the case. All dependencies that have a single version are moved to the catalog. I expected only dependencies used in multiple packages would be moved.
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 with the README statement about dependencies used by more than two packages, then trace the catalog migration behavior to determine why single-version dependencies are included. Compare the implementation with the documented rule and verify that only dependencies shared by multiple packages are moved to the catalog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100