A new post of our interview series “Meeting the stars of the R-universe”. We aim to introduce the teams and people behind the development of software and packages many of us use and which are available through the R-Universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users.
This is the second post of our interview series “Meeting the stars of the R-universe”. We aim to introduce the working groups and people behind the development of software and packages many of us use and which are available through the R-universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users.
Finding the right tool for the job The hardest part about effectively using R is finding the best packages for the problem you are trying to solve. I think this is even more important than being fluent in the language itself, which you will pick up along the way as you start using R more frequently. However, building your code on reliable foundations is essential for good results, and difficult to fix later on in a project.
Running your own package registry Tiny update for r-universe users whos run their own package registry: we have changed the preferred git repo name where you host your packages.json registry file. Previously the git repository was simply called universe, i.e. the registry for tiledb-inc.r-universe.dev was in the GitHub repository tiledb-inc/universe.
ul a:hover{text-decoration: underline;}Pretty permanent URLs! We have improved the URL schema for the r-universe.dev front-end to make it even easier to find and share a link to an R package, article, API, or other resource. The old URLs will now automatically be redirected to the new locations, so this should be a non-breaking change.
Two new packages! We released two new packages that we are using in r-universe to render package documentation: postdoc and prismjs. The goal of postdoc is very simple: generate beautiful single-page package manuals in HTML format. Postdoc uses our prismjs and katex packages for server-side highlighting and math.
This is the first post of our interview series “Meeting the stars of the R-universe” . We aim to introduce the working groups and people behind the development of software and packages many of us use and which are available through the R-Universe . We want to highlight and explore different teams and projects around the world, the work they do, their processes and users.
R-universe now has search! We made a series of structural improvements in r-universe to make it easier to browse and discover interesting R packages and articles. Most notably, the r-universe.dev landing page has been overhauled: you can now search directly for any name or keyword across the entire ecosystem: The homepage also lists the popular topics and organizations, and links to recently active packages, articles, and maintainers.
The rOpenSci R-universe is a bit special as, compared to other R-universes, it builds docs for all the packages in our suite.Looking at the dashboard helps us identify failures in building the packages as well as in building the pkgdown websites.We then help authors fix these issues in order to comply with our package curation policy.As a package author you should also rely on continuous integration in your own repo for catching e.g. R CMD check
What is renv RStudio’s renv package is a powerful dependency management toolkit for R. It allows you to create a lockfile that records the exact versions of R packages used in a given project, and provides tooling to install exactly those same versions on another machine, or at a later point in time. This is very useful to create an isolated project environment for reproducibility or production purposes.
