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.
176 results across 1 active filter
Page 6 of 8
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Wraps widget creation, listeners, observers, timers, and destruction in one lifecycle boundary and verifies repeated navigation does not accumulate resources.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.
Tests input replacement, DOM events, computed rendering, and stable identity without forcing change detection around missing notifications.
Explains component tests that assert user-visible behavior instead of implementation details.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Diagnoses aliasing and shallow-copy mistakes, then restores explicit state ownership and immutable update boundaries.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains when a reducer clarifies related state transitions and when independent state remains simpler.
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 closures as functions retaining access to lexical bindings, then connects them to callbacks, factories, state, and common capture mistakes.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.