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.
102 results across 1 active filter
Page 4 of 5
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
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.
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.
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.
Balances strict script policy with per-request nonces, dynamic rendering, third-party scripts, caching, and operational rollout.
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.
Covers Promise-based params and search parameters, async request APIs, generated route types, and runtime validation.
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.
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.