A dependency management toolkit for R. Using 'renv', you can create and manage project-local R libraries, save the state of these libraries to a 'lockfile', and later restore your library as required. Together, these tools can help make your projects more isolated, portable, and reproducible.
Version: | 0.11.0 |
Imports: | utils |
Suggests: | covr, knitr, packrat, remotes, reticulate, rmarkdown, rstudioapi, testthat, uuid, yaml |
Published: | 2020-06-26 |
Author: | Kevin Ushey [aut, cre], RStudio [cph] |
Maintainer: | Kevin Ushey <kevin at rstudio.com> |
BugReports: | https://github.com/rstudio/renv/issues |
License: | MIT + file LICENSE |
URL: | https://rstudio.github.io/renv |
NeedsCompilation: | no |
Materials: | README NEWS |
In views: | ReproducibleResearch |
CRAN checks: | renv results |
Reference manual: | renv.pdf |
Vignettes: |
Using renv with Continuous Integration Collaborating with renv Using renv with Docker Frequently Asked Questions Installing from Local Sources Anatomy of a Lockfile Using MRAN Binaries Package Development with renv Using Python with renv Introduction to renv |
Package source: | renv_0.11.0.tar.gz |
Windows binaries: | r-devel: renv_0.11.0.zip, r-release: renv_0.11.0.zip, r-oldrel: renv_0.11.0.zip |
macOS binaries: | r-release: renv_0.11.0.tgz, r-oldrel: renv_0.11.0.tgz |
Old sources: | renv archive |
Reverse imports: | learnr |
Reverse suggests: | HaDeX, worcs |
Please use the canonical form https://CRAN.R-project.org/package=renv to link to this page.