vendor

Calling <code>renv:::vendor()</code> will:<ul>
<li>Compile a vendored copy of renv to <code>inst/vendor/renv.R</code>,</li>
<li>Generate an renv auto-loader at <code>R/renv.R</code>.</li>
</ul>Using this, projects can take a dependency on renv, and use renv
internals, in a CRAN-compliant way. After vendoring renv, you can
use renv APIs in your package via the embedded renv environment;
for example, you could call the <code>dependencies()</code> function with:
<div class="sourceCode"></div><pre><code>renv$dependencies()
</code></pre>
Be aware that renv internals might change in future releases, so if you
need to rely on renv internal functions, we strongly recommend testing
your usages of these functions to avoid potential breakage.

internal

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.

Kevin Ushey

renv

Project Environments

Hadley Wickham

Posit Software, PBC 

vendor function

<dl><dt>version</dt>
<dd>The version of renv to vendor. <code>renv</code> sources will be pulled
from GitHub, and so <code>version</code> should refer to either a commit hash or a
branch name.</dd>
<dt>project</dt>
<dd>The project in which renv should be vendored.</dd></dl>

Arguments

Calling <code>renv:::vendor()</code> will:<ul>
<li>Compile a vendored copy of renv to <code>inst/vendor/renv.R</code>,</li>
<li>Generate an renv auto-loader at <code>R/renv.R</code>.</li>
</ul>

Using this, projects can take a dependency on renv, and use renv
internals, in a CRAN-compliant way. After vendoring renv, you can
use renv APIs in your package via the embedded renv environment;
for example, you could call the <code>dependencies()</code> function with:
<div class="sourceCode"><pre><code>renv$dependencies()
</code></pre></div>
Be aware that renv internals might change in future releases, so if you
need to rely on renv internal functions, we strongly recommend testing
your usages of these functions to avoid potential breakage.

Vendor renv in an R package — vendor

<dl>

<dt>version</dt>
<dd>The version of renv to vendor. <code>renv</code> sources will be pulled
from GitHub, and so <code>version</code> should refer to either a commit hash or a
branch name.</dd>


<dt>project</dt>
<dd>The project in which renv should be vendored.</dd>

</dl>

vendor: Vendor renv in an R package

Description

Usage

Arguments