Loading
Pick a focused question that fits your time, stack, and interview goal.
86 results across 1 active filter
Page 2 of 4
Explains client cache keys, freshness, invalidation, refetching, optimistic updates, and server truth.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Places segment and global boundaries deliberately, separates expected errors, and makes retries observable and safe.
Explains context propagation, value identity, provider scope, domain separation, and measured optimization.
Explains named slots, retained active state, hard-navigation fallbacks, and the required default files in Next.js 16.
Explains DOM relocation, React-tree event propagation, accessible modal focus, and layering constraints.
Chooses tag and path invalidation based on data identity, consistency requirements, and affected route surfaces.
Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.
Separates interruptible background rendering from time-based event or request suppression.
Combines a canonical detail page with an intercepted modal, Parallel Route slot, browser history, and accessible dismissal.
Repairs unstable Hook order caused by branches, early returns, callbacks, loops, or exception paths.
Moves from a reproducible user interaction to render evidence, root cause, proportional repair, and field validation.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Combines server and client instrumentation, OpenTelemetry, post-response work, correlation, and privacy-aware signals.
Owns a third-party widget through a DOM ref, effect lifecycle, minimal updates, and complete teardown.
Models pending, validation, success, retry, and authoritative server outcomes around a React 19 form Action.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Splits meaningful code, keeps stable UI visible, preloads likely paths, and pairs loading with error recovery.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Tests user-observable urgent, pending, success, failure, interruption, and out-of-order behavior without scheduler coupling.
Uses route groups for organization and layout boundaries while accounting for URL collisions and full reloads across roots.
Designs optimistic identity, pending state, reconciliation, rollback, and overlapping mutation behavior.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.