Tools to Make Developing R Packages Easier
Coerce input to a package.
Open bash shell in package directory.
Create package pdf manual
Build a Rmarkdown files package
Execute pkgdown build_site in a package
Build package vignettes.
Build package
Check a package on macOS
Check documentation, as R CMD check does.
Run CRAN checks for package on R-hub
Check a package on Windows
Build and check a package
Clean built vignettes.
Create a package
Activate and deactivate development mode
Return a vector of names of packages loaded by devtools
Report package development situation
Deprecated Functions
devtools: Tools to Make Developing R Packages Easier
Use roxygen to document a package.
Git checks.
Was devtools installed with tests?
Install package dependencies if needed.
Install a local development package.
Is the object a package?
Lint all source files in a package
Load complete package
Return a vector of names of attached packages
Find missing s3 exports.
Find file in a package.
Environment variables to set when calling R
Objects exported from other packages
Custom devtools release checks.
Release package to CRAN.
Unload and reload package.
Functions re-exported from the remotes package
Reverse dependency tools.
Run all examples in a package.
Save all documents in an active IDE session.
Show package news
Run a script on gist
Run a script through some protocols such as http, https, ftp, etc.
Spell checking
Submit a package to CRAN
Execute testthat tests in a package
Uninstall a local development package
Does a package use testthat?
Set working directory.
Collection of package development tools.
Useful links