In yonicd/craninfo: On demand CRAN checks for your current R session

knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  fig.path = "man/figures/README-",
  out.width = "100%"
)

craninfo

The goal of checkinfo is to surface CRAN checks information into a sessioninfo output specific to the user's platform.

Installation

# install.packages("remotes")
remotes::install_github("yonicd/craninfo")

Example

This is a basic example which shows you how to solve a common problem:

library(craninfo)

On CRAN each package is continually checked to see if there are any problems with it on a variety of platforms and this information is always available for package users to view.

cchecks is an R package that uses an API to retrieve information from these tests in an efficient manner.

Here is the output from dplyr

(cchecks::cch_pkgs('dplyr'))$data$checks

What if you wanted to use this same information to create an output similar to sessioninfo, but append to it the information from the current CRAN checks for each loaded namespace (package) tailored to your platform.

This is what craninfo does for you!

With this information you can

• See if there are any problems with the packages that you are using in an R/Rmd script
• Attach it to a {reprex} to help the maintainer help you even more efficiently.
• See if you have the most current version of a package installed, and if not you can decide if you should install it given it's current CRAN status.
• Compare multiple CRAN check flavors with ease.

Console Output

Current CRAN release

craninfo()

Compare CRAN releases

craninfo(cran_type = c('release','oldrel'))

yonicd/craninfo documentation built on June 13, 2020, 5:14 p.m.