Test your Lit knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What does it mean that Lit performs "efficient, targeted DOM updates" rather than re-rendering the whole component on every state change?
In this round
What does it mean that Lit performs "efficient, targeted DOM updates" rather than re-rendering the whole component on every state change?
What is Lit SSR (Server-Side Rendering) support intended to address?
What is `lit-html` (as distinct from the full `lit` package / `LitElement`)?
What is the significance of Lit's templates NOT requiring a compile step (unlike JSX, which needs Babel/TypeScript to transform)?
What is a "Web Component" (the underlying browser standard Lit builds on), independent of any specific library?
What is a common reason a design-system/component-library team might specifically choose Lit over building components in a single framework like React?
What is the difference between binding a value to an HTML attribute versus a DOM property in a Lit template, e.g. `?disabled=${isDisabled}` versus `.value=${text}`?
What is the purpose of Lit's `@eventName=${handler}` syntax in a template?
What are "custom events" in the context of a Lit component communicating with its parent/consumer?
What does Lit's TypeScript decorator syntax (`@customElement('my-element')`, `@property()`, `@state()`) provide compared to the equivalent plain-JavaScript static field declarations?
What is Shadow DOM, and how does Lit use it by default?
What is the purpose of the `css` tagged template literal in Lit, used alongside a component's `static styles` field?