Build and check a package, cleaning up automatically on success.

check automatically builds and checks a source package, using all known best practices. check_built checks an already built package.

check(pkg = ".", document = NA, build_args = NULL, ...,
  manual = FALSE, cran = TRUE, remote = FALSE, incoming = remote,
  force_suggests = FALSE, run_dont_test = FALSE, args = "--timings",
  env_vars = NULL, quiet = FALSE, check_dir = tempdir(),
  cleanup = TRUE, error_on = c("never", "error", "warning", "note"))

check_built(path = NULL, cran = TRUE, remote = FALSE, incoming = remote, force_suggests = FALSE, run_dont_test = FALSE, manual = FALSE, args = "--timings", env_vars = NULL, check_dir = tempdir(), quiet = FALSE, error_on = c("never", "error", "warning", "note"))


The package to use, can be a file path to the package or a package object. See as.package() for more information.


If NA and the package uses roxygen2, will rerun document() prior to checking. Use TRUE and FALSE to override this default.


Additional arguments passed to R CMD build


Additional arguments passed on to pkgbuild::build().


If FALSE, don't build and check manual (--no-manual).


if TRUE (the default), check using the same settings as CRAN uses.


Sets _R_CHECK_CRAN_INCOMING_REMOTE_ env var. If TRUE, performs a number of CRAN incoming checks that require remote access.


Sets _R_CHECK_CRAN_INCOMING_ env var. If TRUE, performs a number of CRAN incoming checks.


Sets _R_CHECK_FORCE_SUGGESTS_. If FALSE (the default), check will proceed even if all suggested packages aren't found.


Sets --run-donttest so that tests surrounded in \dontest{} are also tested. This is important for CRAN submission.


Additional arguments passed to R CMD check


Environment variables set during R CMD check


if TRUE suppresses output from this function.


the directory in which the package is checked compatibility. args = "--output=/foo/bar" can be used to change the check directory.




Whether to throw an error on R CMD check failures. Note that the check is always completed (unless a timeout happens), and the error is only thrown after completion. If "never", then no errors are thrown. If "error", then only ERROR failures generate errors. If "warning", then WARNING failures generate errors as well. If "note", then any check failure generated an error.


Path to built package.


Passing R CMD check is essential if you want to submit your package to CRAN: you must not have any ERRORs or WARNINGs, and you want to ensure that there are as few NOTEs as possible. If you are not submitting to CRAN, at least ensure that there are no ERRORs or WARNINGs: these typically represent serious problems.

check automatically builds a package before calling check_built as this is the recommended way to check packages. Note that this process runs in an independent realisation of R, so nothing in your current workspace will affect the process.


An object containing errors, warnings, and notes.

Environment variables

Devtools does its best to set up an environment that combines best practices with how check works on CRAN. This includes:

  • The standard environment variables set by devtools: r_env_vars(). Of particular note for package tests is the NOT_CRAN env var which lets you know that your tests are not running on CRAN, and hence can take a reasonable amount of time.

  • Debugging flags for the compiler, set by compiler_flags(FALSE).

  • If aspell is found _R_CHECK_CRAN_INCOMING_USE_ASPELL_ is set to TRUE. If no spell checker is installed, a warning is issued.)

  • env vars set by arguments incoming, remote and force_suggests

See Also

release() if you want to send the checked package to CRAN.

  • check
  • check_built
Documentation reproduced from package devtools, version 2.2.0, License: GPL (>= 2)

Community examples

Looks like there are no examples yet.