Project Environments
Modify a Lockfile
Path for storing global state
Retrieve the active project
Activate or deactivate a project
Auto-load the active project
Checkout a repository
Clean a project
User-level settings
Consent to usage of renv
Find R package dependencies in a project
Print a diagnostics report
Capture and re-use dependencies within a .R or .Rmd
Install required system libraries
Generate a Package Dependency Graph
View and revert to a historical lockfile
Copy packages from user libraries to a project library
Imbue an renv Installation
Use renv in a project
Install packages
Isolate a project
Load a project
Programmatically Create and Modify a Lockfile
Lockfiles
Migrate a project from packrat to renv
Purge packages from the cache
Rebuild the packages in your project library
Update package records in a lockfile
Refresh the local cache of available packages
Re-hash packages in the renv cache
Resolve a Remote
Remove packages
Project-local Environments for R
Generate renv.lock from an RStudio Connect manifest.json
Repair a project
Restore project library from a lockfile
Run a script
The default library sandbox
Generate project infrastructure
Project settings
Record current state of the project library in the lockfile
Report inconsistencies between lockfile, library, and dependencies
Update packages
Upgrade renv
Use python
Vendor renv in an R package
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.
Useful links