This function must be called from a Shiny app's UI in order for all other
shinyjs
functions to work.
You can call useShinyjs()
from anywhere inside the UI, as long as the
final app UI contains the result of useShinyjs()
.
useShinyjs(rmd = FALSE, debug = FALSE, html = FALSE)
Set this to TRUE
only if you are using shinyjs
inside an interactive R markdown document. If using this option, view the
README online to learn how to
use shinyjs in R markdown documents.
Set this to TRUE
if you want to see detailed debugging
statements in the JavaScript console. Can be useful when filing bug reports
to get more information about what is going on.
Set this to TRUE
only if you are using shinyjs
in
a Shiny app that builds the entire user interface with a custom HTML file. If
using this option, view the
README online to learn
how to use shinyjs in these apps.
Scripts that shinyjs
requires that are automatically inserted
to the app's <head>
tag. A side effect of calling this function is that
a shinyjs
directory is added as a resource path using
shiny::addResourcePath()
.
If you're a package author and including shinyjs
in a function in your
your package, you need to make sure useShinyjs()
is called either by
the end user's Shiny app or by your function's UI.
if (interactive()) {
library(shiny)
shinyApp(
ui = fluidPage(
useShinyjs(), # Set up shinyjs
actionButton("btn", "Click me"),
textInput("element", "Watch what happens to me")
),
server = function(input, output) {
observeEvent(input$btn, {
# Run a simply shinyjs function
toggle("element")
})
}
)
}