Vue, Nuxt, and Angular

This domain is tested comparatively: Vue is a progressive UI framework with fine-grained reactivity, Nuxt adds application conventions on top of Vue (routing, rendering, server), and Angular is a full TypeScript platform with dependency injection, RxJS, and opinionated structure.

Child sections cover Vue core (Composition API, Options API, reactivity, router, Pinia), Nuxt (file routing, SSR/SSG, data fetching, Nitro), and Angular (components, services, DI, RxJS, forms, routing).

On interviews: expect when you would pick each stack, how reactivity and rendering differ, what belongs in framework primitives versus libraries, and how SSR or routing changes architecture.

Common pitfalls: describing Vue as "React with different syntax", Nuxt as "only a router", or Angular as "only components". Name conventions, runtime model, team scale, deployment shape, and ecosystem trade-offs.

Checklist:

• Contrast framework scope and adoption path.
• Name each reactivity and rendering model.
• Explain routing and SSR ownership.
• Discuss team and maintenance trade-offs.