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.
162 results across 1 active filter
Page 6 of 7
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Explains why external data needs runtime validation even when the application uses TypeScript.
Balances strict script policy with per-request nonces, dynamic rendering, third-party scripts, caching, and operational rollout.
Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.
Uses functional interceptors for cross-cutting transport concerns without hiding domain behavior or unsafe retries.
Keeps Next.js 16 Proxy focused on request routing and optimistic checks rather than data access or final authorization.
Defines the serializable prop boundary, component composition pattern, and protections against leaking server-only data.
Handles eager subscription, initial values, injection context, errors, cleanup, and repeated conversions.
Covers Promise-based params and search parameters, async request APIs, generated route types, and runtime validation.
Explains assignability by shape, excess-property checks, and the gap between compile-time compatibility and runtime identity.
Separates React's pure calculation work from DOM mutation, layout effects, passive effects, and browser paint.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Tests rendered behavior, user interaction, outputs, and visible failure states without coupling to private implementation details.
Renders a measured window while preserving identity, scrolling, accessibility, dynamic sizes, and interaction state.
Uses harnesses for reusable or complex widgets where a stable user-oriented test API is more valuable than direct DOM coupling.
Treats memoization as measured performance work and accounts for prop identity, context, readability, and React Compiler.
Uses derived types for genuine relationships while preserving explicit boundaries for domain and transport models.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
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.
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Exposes a small focus, scroll, or media API while keeping component internals private and preferring declarative props.
Defers non-critical UI with deliberate triggers, placeholders, prefetching, and hydration behavior while protecting core interactions.
Separates declared variable types, unchecked developer assertions, and compatibility checking that preserves useful inferred types.