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 3 of 8
Separates projected caller-owned content from a component's own view and explains when queries are justified.
Places segment and global boundaries deliberately, separates expected errors, and makes retries observable and safe.
Explains contextual sanitization and treats bypass APIs as narrow security-review decisions rather than general encoding helpers.
Connects environment and element injectors to instance lifetime, overrides, lazy routes, and accidental state isolation.
Relates JavaScript classes to prototype-based delegation while preserving the useful semantics class syntax adds.
Explains context propagation, value identity, provider scope, domain separation, and measured optimization.
Explains DOM and CSSOM construction, style, layout, paint, and compositing as a practical performance model.
Uses generics to preserve relationships between types and constraints to express the operations an implementation requires.
Explains the notification paths Angular relies on and designs components that do not depend on incidental global checks.
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.
Compares JavaScript declarations through scope, initialization, redeclaration, reassignment, and practical default choices.
Chooses template-driven, typed reactive, or experimental Signal Forms based on workflow complexity and stability needs.
Chooses interfaces or aliases based on object contracts, unions, composition, declaration merging, and team consistency.
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.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.
Keeps server and client output compatible while isolating browser APIs, user state, and post-render integration.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Overrides dependencies at the provider boundary while preserving the same injection scope and contract used in production.