You can either just look at the top comment when you load R Console or R Studio: T’s important to first check the R version. Alas, I needed to update R to the latest version, and in the process decided to update RStudio as well. This path becomes ~/Library/R/3.5/library.Because R and R Studio don’t necessarily warn you when they need upgrading, I had to figure it out myself when I started getting some weird bugs running assignments during an R class. The %v isĪutomatically expanded to the major and minor version of R, so with R 3.5.1 You can also alternatively set R_LIBS_USER to a different path but make sure The directory may not already exist, so one option is just to create thisĭirectory ( fs::dir_create(Sys.getenv('R_LIBS_USER'))). ~/R/win-library/x.y on Windows and ~/Library/R/x.y/library on macOS) but R_LIBS_USER is actually set by default to this scheme, (to

Make sure the package library is specific to the minor version of R. Re-install R if needed without touching your CRAN packages. Packages separate from the rest of your packages. I suggest you keep the packages R comes with (base and recommended) While it may work some (even most) of the time, R-core does not guarantee compatibility between these versions and things could break (even break silently). You may see some suggestions that you can just copy your packages even when the ‘minor’ version changes.

12.3 Where things exist in CRAN packages.

12.2 Where things exist in the R source.