Shiny is an R package from RStudio that makes it incredibly easy to build interactive web applications with R. Behind the scenes, Shiny builds a reactive graph that can quickly become intertwined and difficult to debug. reactlog provides a visual insight into that black box of Shiny reactivity.
After logging the reactive interactions of a Shiny application, reactlog constructs a directed dependency graph of the Shiny’s reactive state at any time point in the record. The reactlog dependency graph provides users with the ability to visually see if reactive elements are:
There are many subtle features hidden throughout reactlog. Here is a short list quickly describing what is possible within reactlog:
For a more in-depth explanation of reactlog, please visit the reactlog vignette.
To install the stable version from CRAN, run the following from an R console:
For the latest development version:
Or while your Shiny app is running, press the key combination
Cmd+F3) to launch the reactlog application.
To mark a specific execution time point within your Shiny app, press the key combination
Cmd+F4). This will highlight a specific point in time in your reactlog.
The best place to get help with Shiny and reactlog is RStudio Community. If you’re having difficulties with reactlog, feel free to ask questions here. For bug reports, please use the reactlog issue tracker.
By changing the file
'./inst/reactlog/defaultLog.js' with the contents of any log file in
'./inst/reactlog/reactlogAsset/reactlog.js') has been built with
yarn build or
yarn watch, refresh
'./inst/reactlog/reactlog.html' to avoid constantly spawning Shiny applications for testing.
We welcome contributions to the reactlog package. Please see our CONTRIBUTING.md file for detailed guidelines of how to contribute.
Please note that the reactlog project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.