The problem
By the mid-2010s React had made it popular to build a UI as a tree of components, but it wrote the markup in JavaScript (JSX), every change went through setState, and shared state often brought Flux or Redux on top. AngularJS kept the markup in HTML, but came with a world of its own: scopes, the digest cycle, dependency injection. Developers wanted components that were easy to start with: an HTML template and state you simply change.
The idea
A component bundles a template, its state and its behaviour, and an app is a tree of components. The state is plain data made reactive: Vue records which properties a render read (Vue 2 with getters and setters, Vue 3 with Proxies), so an ordinary this.todos.push(...) is enough to update the page. The template is HTML with directives: v-for repeats an element, :class binds a class, v-model keeps a form field and a property in sync, @submit.prevent attaches a handler.
Angular 2 (2016) built apps from component classes and their HTML templates. Svelte (2016) moved the work into a compiler that turns each component into small standalone JavaScript at build time.
What hurt next
These apps still rendered in the browser. The server sent an almost empty page, and nothing useful appeared until the framework and the app's JavaScript had downloaded and run; crawlers and link previews that do not run JavaScript saw nothing. Routing, server rendering, code splitting and data loading were left to each team to put together. Meta-frameworks such as Next.js and Nuxt bundled those pieces around the component framework and rendered pages on the server or at build time.
How close this is to the original
Runs Vue 3.5.45, the full build with the template compiler, in development mode. The component uses the Options API, the style of Vue 1 and 2 code (2015–2020) that Vue 3 still supports. Two details are newer: Vue 1 and 2 started an app with new Vue({ el: "#app", data: { ... } }), which Vue 3 replaced with createApp(...).mount("#app"), and data must now be a function that returns the state. Many projects wrote single-file .vue components compiled by a build tool; here the template sits in the page and is compiled in the browser.