Background

This section captures the design rationale behind some of Vue's choices — the "why" behind decisions that show up everywhere in the source. It is not a substitute for the RFC repo which is the authoritative record; it is a curated tour of decisions that matter to anyone reading the code.

Pages

• Design decisions — the major architectural choices: Proxy-based reactivity, monorepo layout, compiler/runtime separation, patch flags, tree-shakable builds.

Reading order

If you are evaluating Vue 3's internals against alternatives, design decisions is the right place to start. If you are debugging or contributing, the package- and feature-level pages are usually more directly useful; come back here when you find yourself wondering "why isn't this implemented differently?".