Test your Stimulus knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a Stimulus controller "value" (declared via the `static values` property), and what does it provide?
Questions in this quiz
What is a Stimulus controller "value" (declared via the `static values` property), and what does it provide?
How would you register a new Stimulus controller class with the application?
What is the relationship between Stimulus and Turbo (both part of the "Hotwire" approach from Basecamp)?
What is a "class" (declared via `static classes`) in a Stimulus controller, and how does it differ from a target?
How does Stimulus connect a JavaScript controller to a specific piece of HTML?
What role does a `data-[controller]-[value]-value` attribute play when a controller's associated HTML is dynamically updated (e.g. via a Turbo Stream response replacing part of the page)?
What is a reasonable criterion for choosing Stimulus (plus Turbo/Hotwire) versus a full SPA framework (React, Vue) for a new web application?
What does Stimulus's `connect()` and `disconnect()` lifecycle callback methods do on a controller?
What is the general performance/bundle-size consideration often cited as an advantage of Stimulus compared to a full SPA framework?
What is Stimulus?
What is a potential downside of Stimulus's "HTML/DOM as source of truth" approach for a page with genuinely complex, deeply interdependent client-side state (many pieces of UI needing to react to each other's changes)?
What is a key architectural difference between Stimulus and a typical component-based framework like React, in terms of where the "source of truth" for UI state lives?