Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
86 results across 1 active filter
Page 4 of 4
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Renders a measured window while preserving identity, scrolling, accessibility, dynamic sizes, and interaction state.
Treats memoization as measured performance work and accounts for prop identity, context, readability, and React Compiler.
Separates reactive synchronization inputs from non-reactive logic that still needs the latest props or state.
Separates missing resources, canonical navigation, authorization outcomes, expected failures, and unexpected exceptions.
Exposes a small focus, scroll, or media API while keeping component internals private and preferring declarative props.
Keeps input and direct feedback urgent while rendering expensive navigation or result updates as interruptible work.
Connects layouts and templates to navigation, state lifetime, Effects, and deliberate remounting in the App Router.
Distinguishes render-driving state from instance-local mutable values and DOM references.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Chooses post-paint synchronization by default and reserves layout effects for pre-paint measurement or correction.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Defines a coherent subscription and snapshot contract for state owned outside React, including server rendering.
Uses development-only repeated rendering, Effects, and ref callbacks to expose impurity and missing cleanup.