packrat::status() should distinguish direct vs. indirect deps
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
E.g. for a project containing a single source file with library(knitr):
> packrat::status()
The following packages are referenced in your code, but are not present
in your library nor in packrat:
digest
evaluate
formatR
highr
knitr
markdown
mime
You will need to install these packages manually, then use
packrat::snapshot() to record these packages in packrat.
It would be more appropriate to single out knitr and then list derived dependencies afterwards.
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 packrat::status() and trace how the example project’s referenced packages are reported. The change is complete when knitr is identified as the direct dependency and its derived dependencies are listed separately, matching the requested distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100