VitePress 1.0 replaces VuePress for docs
VitePress 1.0 replaces VuePress, powering docs for Vite, Pinia, and Vitest. It serves static HTML for SEO, then hydrates into a Vue 3 SPA with sub-100ms edits. Migrate legacy VuePress docs or choose it for new content sites.
Vue 3.5 cuts reactivity memory 56%, adds lazy hydration
Vue 3.5 drops reactivity memory 56% and large arrays up to 10x faster with no breaks. Stable reactive props destructure kills withDefaults boilerplate, while lazy hydration and useId() fix SSR pain points.
Describe a Nuxt server caching strategy for slow upstream APIs
Tests server-side caching architecture in Nuxt Nitro. A strong answer proposes a server middleware or route handler with Redis or LRU in-memory cache, sets TTL per endpoint, and handles cache invalidation.
Angular Universal server memory leak: causes and diagnosis
WHAT IT TESTS: Angular SSR platform lifecycle in Node.js and cross-request retainers. ANSWER OUTLINE: incomplete platform destruction, global DOM polyfills, unclosed RxJS; use heap snapshots and --inspect. RED FLAG: blaming Angular, not citing request cleanup.
How do you debug and fix flaky Cypress E2E tests?
This tests systematic debugging of async UI behavior. A strong answer isolates root causes via logs and screenshots, fixes races with explicit waits or intercepts, and stubs APIs not network timing.
What is the difference between ChangeDetectionStrategy.Default and ChangeDetectionStrategy.OnPush in Angular?
WHAT IT TESTS: Angular change detection and subtree skipping. ANSWER OUTLINE: Default checks components on most async events; OnPush checks on input changes, DOM events, or async pipe emits. RED FLAG: OnPush is not a free switch; it requires immutable data.
How do Vue, Angular, and Svelte stores trigger component re-renders?
Tests deep knowledge of reactivity primitives. Contrast Vue's proxy subscriptions, Angular's RxJS push through async pipe or markForCheck, and Svelte's compiler-generated store invalidation. Red flag: claiming all three use virtual DOM diffing or polling.
Pass server state to client in Nuxt and name the composable
This tests Nuxt SSR state hydration. A strong answer names useState, explains server values serialize to JSON for client hydration, and warns against refs defined outside setup.
What is Angular Ivy's 'locality' and its benefits over View Engine?
Tests Ivy's per-file compilation model. Locality compiles decorators to static properties without global knowledge, except components need their NgModule scope, speeding builds and tree-shaking.
How does ngc work in Angular AOT and what artifacts improve performance?
This tests understanding of AOT build-phase compilation and output. Cover efficient JS output, inlined templates and styles cutting AJAX requests, and removal of compiler payload roughly half of Angular. Red flag: conflating AOT and JIT or calling it bundling.
How would you unit-test a Svelte date utility with Vitest?
This question tests isolating pure logic from Svelte and configuring Vitest. A good answer covers installing Vitest, co-locating a spec file, and asserting known inputs. A red flag is insisting you must mount a Svelte component to test a plain function.
How would you implement a memoized selector for expensive derived state?
It tests cache invalidation and pure functions for reactive derived state. A strong answer covers reference tracking on inputs, returning cached results when unchanged, and requiring immutable or stable arguments.
How would you structure a scalable store for interconnected domains?
Tests domain-driven state partitioning and cross-slice derived data. Strong answers use feature slices, normalized entities, and memoized selectors; keep computed state out of the store. Red flag: a monolithic state tree with component-level recomputation.
Create a custom synchronous validator for an Angular Reactive Form
Tests your grasp of the ValidatorFn contract and reactive form wiring. A strong answer: a function accepting AbstractControl returns null when valid or an error object when invalid, passed as the second FormControl argument. Red flag: returning booleans.
How do Vue, Angular, and Svelte handle deep prop mutation re-rendering?
WHAT IT TESTS: Deep reactivity vs zone-driven dirty checking. ANSWER OUTLINE: Vue and Svelte detect nested mutations via Proxies; Angular default re-renders via Zone.js, but ngOnChanges misses it since the reference is unchanged.
How does Angular's Zone.js change detection differ from Vue and Svelte reactivity?
Tests granular reactivity architecture. Angular Zone.js monkey-patches async to scan the full component tree; Vue uses runtime Proxy tracking; Svelte compiles runes into targeted DOM bindings.
Compare SSR, SSG, and ISR trade-offs in meta-frameworks
What it tests: matching rendering modes to build time, freshness, and scale. Outline: contrast SSR per-request cost with SSG fast CDN delivery but stale content and long builds, then show ISR as lazy regeneration post-deploy.
Explain server.ts and main.ts in Angular Universal
WHAT IT TESTS: Angular SSR entry points and hydration. ANSWER OUTLINE: server.ts SSRs initial HTML via Node/Express; main.ts bootstraps the browser app and hydrates the DOM. First request hits the server; later navigations are client-side only.
How do you create a POST API endpoint in SvelteKit?
WHAT IT TESTS: Filesystem routing and server-only API routes in SvelteKit. ANSWER OUTLINE: Add a +server.js file in a src/routes subdirectory, export a POST handler returning a Response, and note that +server files never run in the browser.
What is the purpose of +page.server.js in SvelteKit?
WHAT IT TESTS: Server-only load boundaries in SvelteKit. ANSWER OUTLINE: Exclusively server-side load feeding the data prop, used for secrets like DB queries and private env vars. RED FLAG: Claiming it runs in the browser or equating it with +page.js.