box
Write reusable, composable and modular R code (by klmr)
sys
Easily create reusable command line scripts with R (by klmr)
Our great sponsors
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
box
Posts with mentions or reviews of box.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-04.
-
Can someone explain how R project are organized and deployed?
As for organising code within a project, as mentioned packages really don’t allow this beyond collation order. The best solution in this space is the ‘box’ package which implements a fully-featured module system for R. ‘box’ notably gets used by some folks to implement large-scale Shiny applications; if this is what you’re after, I would recommend the ‘rhino’ framework, which builds upon Siny and ‘box’.
-
Does anyone feel like R is actually vastly worse for dependency/environment management than Python?
I would look into box https://github.com/klmr/box if you haven’t heard of it already
-
"Managing large codebases in R" webinar (Oct. 6, 2022)
Shapeless plug: check out the already mentioned ‘box’, I think it’s strictly superior to ‘import’ (but I’m biased).
-
Restructuring a large R project. Need advice on how to wire up file paths and associated objects.
I think your use-case is best addressed by the ‘targets’ package. But I would also recommend checking out the ‘box’ package for a more general way of structuring R projects in modules which isn’t supported well natively by R (disclaimer: I wrote that package). Writing R code as modules fundamentally side-steps the issue of having to deal with absolute paths. Instead, all code and data are either contained in the module or can be accessed relative to the working directory.
-
How do you organize your code snippets/notes?
Check out ‘box’, it’s designed precisely to solve (most of) your issues. Namely, it allows you to organise your R code files into (nested) modules, which can either be part of one project, or they can be stored centrally, and reused seamlessly across projects. It also allows you to document your code and makes this documentation available just like package documentation.
-
Creating your own R package
I'll also name drop the Box package, which serves like a middle of the road option between creating packages and sourcing scripts. It allows you to treat scripts (and the functions inside them) like packages without having to go through all the extra steps to build packages. In that way, it's more similar to creating and importing python modules.
-
import functions from a package without loading the package
I don't fully understand what happens when you attach a package, so I can't speak to your question about side-effects. However, if you're looking for an alternative, possibly safer, strategy, you might try the package box.
There is: use the ‘box’ package. It allows this and more. In your specific case, you’d write
-
Reference project for an R 2+2=4 style application coverage, testthat and a build file
That said, I’ve been playing with a framework for command line applications in R (as a ‘box’ module), and I guess you could call the example application “2+2=4” style (it’s a command line calculator, complete with automatically generated option parser etc.).
-
What would you like to see from an R2 / R++ / R#
You can do that with ‘box’, check it out!
sys
Posts with mentions or reviews of sys.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-31.
-
Reference project for an R 2+2=4 style application coverage, testthat and a build file
Anyway, here’s the code ((outdated!) repo):
Please go a head but note that the current version is depending on a deprecated version of the ‘box’ package (which used to be called ‘modules’). I’m in the process of rewriting it, so please use the work in progress branch (the tests currently don’t work because I broke something during the restructuring; if you’re curious about unit testing with ‘box’, check out the “testing” vignette).
What are some alternatives?
When comparing box and sys you can also consider the following projects:
renv - renv: Project environments for R.
ggplot2 - An implementation of the Grammar of Graphics in R
rnim - A bridge between R and Nim
tidytable - Tidy interface to 'data.table'
workflowr - Organize your project into a research website
lintr - Static Code Analysis for R
rspm - RStudio Package Manager
rocker - R configurations for Docker
fun - Module for functional programming in R
types - Types for R
uktrade - An R package containing convenient functions to load HMRC Overseas Trade Statistics, Regional Trade Statistics, and custom URLs using HMRC's API.
ggplot2-book - ggplot2: elegant graphics for data analysis