We are pleased to announce that our package {attachment} is now available on CRAN. The goal of attachment is to help to deal with package dependencies during package development. It also gives useful tools to install or list missing packages used inside Rscripts or Rmds. Deal with dependencies during package development If you ever had the following error when checking your package, {attachment} is for you: R CMD check results 1 error | 0 warnings | 0 notes checking package dependencies … ERROR Namespace dependency not required: ‘collateral’ With this error, Colin would answer you: Indeed, the steps to deal with dependencies in your RRead More →

Shiny App as a Package In a previous post, I’ve introduced the {golem} package, which is an opinionated framework for building production-ready Shiny Applications. This framework starts by creating a package skeleton waiting to be filled. But, in a world where Shiny Applications are mostly created as a series of files, why bother with a package? This is the question I’ll be focusing on in this blog post. What’s in a Shiny App? OK, so let’s ask the question the other way round. Think about your last Shiny which was created as a single-file (app.R) or two files app (ui.R and server.R). You’ve got theseRead More →

Managing packages in production is a lot of work: you have to juggle between versions, internal packages, CRAN updates, Bioconductor, GitHub sources… Let’s have a look into RStudio Package Manager, one of the tools available that helps you dealing with this. What is love RSPM (Baby don’t hurt me, no more 🎶) RStudio Package Manager (or RSPM for short) is a solution designed to help you to deal with the installation of packages in your organisation. Wether you need to make available to your team the whole CRAN through a proxy, a selection of the CRAN, GitHub packages, internal packages, etc, you can use RSPMRead More →

In this article, I will introduce the approach we use at ThinkR for Shiny applications we design. This is a relatively strict framework but designed to simplify our life and guarantee to deliver a “prod ready” application (whether it is launched locally, on shinyserver, Rconnect or via ShinyProxy with docker). This framework simplifies application maintenance and collaborative work. A Shiny application in a package R A R library model for a Shiny application In this article, I will present an approach, which is still in progress. We have built ShinyApps for a long time now, thus we considered our approach to be mature enough to freezeRead More →