align-deps: add a toggle to show why a dependency got added
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 119
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 52
Description
This command/flag is modeled after yarn why. Example usage:
% rnx-align-deps --why @react-native-community/netinfo
├─ some-package
│ └─ @react-native-community/netinfo (via 'storage')
│
└─ another-package
└─ @react-native-community/netinfo (via 'storage')
align-deps scans the current package (either in the current directory, or the directory specified by the user) for dependencies that require the specified package, including the corresponding capability.
--why is its own command, on the same line with --init, --export-catalogs, --set-version, and is therefore directly incompatible with them. Similarly, it does not invoke a check.
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
Start by locating the align-deps CLI entry point and existing handling for --init, --export-catalogs, and --set-version. Trace how the current package and requested dependency are scanned, then verify that --why is mutually exclusive with those commands and does not invoke a check. Done means the documented tree output identifies requiring packages and capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- cli, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100