Shinyjs
π‘ Easily improve the user experience of your Shiny apps in seconds
Install / Use
/learn @daattali/ShinyjsREADME
<img src="inst/img/hex.png" width="170" align="right"/>
{shinyjs} lets you perform common useful JavaScript operations in Shiny apps that will greatly improve your apps without having to know any JavaScript.
Examples include: hiding an element, disabling an input, resetting an input back to its original value, delaying code execution by a few seconds, and many more useful functions for both the end user and the developer. {shinyjs} can also be used to easily call your own custom JavaScript functions from R.
Need Shiny help? I'm available for consulting.<br/> If you find {shinyjs} useful, please consider supporting my work! β€
<p align="center"> <a style="display: inline-block;" href="https://github.com/sponsors/daattali"> <img height="35" src="https://i.imgur.com/034B8vq.png" /> </a> </p>This package is part of a larger ecosystem of packages with a shared vision: solving common Shiny issues and improving Shiny apps with minimal effort, minimal code changes, and clear documentation. Other packages for your Shiny apps:
| Package | Description | Demo | |---|---|---| | shinyalert | π―οΈ Easily create pretty popup messages (modals) in Shiny | π | | shinyscreenshot | π· Capture screenshots of entire pages or parts of pages in Shiny apps | π | | timevis | π Create interactive timeline visualizations in R | π | | shinycssloaders | β Add loading animations to a Shiny output while it's recalculating | π | | colourpicker | π¨ A colour picker tool for Shiny and for selecting colours in plots | π | | shinybrowser | π Find out information about a user's web browser in Shiny apps | π | | shinydisconnect | π Show a nice message when a Shiny app disconnects or errors | π | | shinytip | π¬ Simple flexible tooltips for Shiny apps | WIP | | shinymixpanel | π Track user interactions with Mixpanel in Shiny apps or R scripts | WIP | | shinyforms | π Easily create questionnaire-type forms with Shiny | WIP |
Table of contents
- Demos and tutorials
- Sponsors π
- Overview of main functions
- Installation
- How to use
- Basic use case - complete working example
- Calling your own JavaScript functions from R
- FAQ and extra tricks
- Support
- Demo Shiny app that lets you play around with some of the functionality in {shinyjs}.
- Video of my {shinyjs} talk (30 min) and the corresponding presentation slides from the 2016 Shiny Developer Conference.
- Video of my {shinyjs} talk (5 min) and the corresponding presentation slides from the 2016 useR Conference.
There are no sponsors yet
Become the first sponsor for {shinyjs} and unlock special rewards!
<h2 id="overview-main"> Overview of main functions </h2>Note: In order to use any {shinyjs} function in a Shiny app, you must
first call useShinyjs() anywhere in the appβs UI.
Functions that help you during Shiny app development
<table> <colgroup> <col style="width: 28%" /> <col style="width: 71%" /> </colgroup> <thead> <tr class="header"> <th>Function</th> <th>Description</th> </tr> </thead> <tbody> <tr class="odd"> <td><code>runcode</code></td> <td>Adds a text input to your app that lets you run arbitrary R code live.</td> </tr> <tr class="even"> <td><code>showLog</code></td> <td>Print any JavaScript <code>console.log()</code> messages in the R console, to make it easier and quicker to debug apps without having to open the JS console.</td> </tr> <tr class="odd"> <td><code>logjs</code></td> <td>Print a message to the JavaScript console (mainly used for debugging purposes).</td> </tr> <tr class="even"> <td><code>inlineCSS</code></td> <td>Easily add inline CSS to a Shiny app.</td> </tr> </tbody> </table>Check out the {shinyjs} demo app
to see some of these in action, or install {shinyjs} and run
shinyjs::runExample() to see more demos.
For most users: To install the stable CRAN version:
install.packages("shinyjs")
For advanced users: To install the latest development version from GitHub:
install.packages("remotes")
remotes::install_github("daattali/shinyjs")
<h2 id="usage">
How to use
</h2>
A typical Shiny app has a UI portion and a server portion. Before using
most {shinyjs} functions, you need to call useShinyjs() in the appβs
UI. Itβs best to include it near the top as a convention.
Here is a minimal Shiny app that uses {shinyjs}:
library(shiny)
library(shinyjs)
ui <- fluidPage(
useShinyjs(), # Include shinyjs
actionButton("button", "Click me"),
textInput("text", "Text")
)
server <- function(input, output) {
observeEvent(input$button, {
toggle("text") # toggle is a shinyjs function
})
}
shinyApp(ui, server)
This is how most Shiny apps should initialize {shinyjs} - by calling
useShinyjs() near the top of the UI.
However, if you use {shinyjs} in any of the following cases:
- In Shiny dashboards (built using the
shinydashboardpackage) - In Shiny apps that use a
navbarPagelayout - In Rmd documents
- In Shiny apps that manually build the user interface with an HTML file or template (instead of using Shinyβs UI func
