- The Vue Instance
- Template Syntax
- Computed Properties and Watchers
- Class and Style Bindings
- Conditional Rendering
- List Rendering
- Event Handling
- Form Input Bindings
- Components Basics
- Component Registration
- Custom Events
- Dynamic & Async Components
- Handling Edge Cases
Transitions & Animation
- Enter/Leave & List Transitions
- State Transitions
Reusability & Composition
- Custom Directives
- Render Functions & JSX
- Single File Components
- TypeScript Support
- Production Deployment
- State Management
- Server-Side Rendering
- Reactivity in Depth
- Migration from Vue 1.x
- Migration from Vue Router 0.7.x
- Migration from Vuex 0.6.x to 1.0
- Migration to Vue 2.7
- Comparison with Other Frameworks
- Join the Vue.js Community!
- Meet the Team
The Vue Instance
Every Vue application starts by creating a new Vue instance with the
Although not strictly associated with the MVVM pattern, Vue’s design was partly inspired by it. As a convention, we often use the variable
vm (short for ViewModel) to refer to our Vue instance.
When you create a Vue instance, you pass in an options object. The majority of this guide describes how you can use these options to create your desired behavior. For reference, you can also browse the full list of options in the API reference.
A Vue application consists of a root Vue instance created with
new Vue, optionally organized into a tree of nested, reusable components. For example, a todo app’s component tree might look like this:
We’ll talk about the component system in detail later. For now, just know that all Vue components are also Vue instances, and so accept the same options object (except for a few root-specific options).
When a Vue instance is created, it adds all the properties found in its
data object to Vue’s reactivity system. When the values of those properties change, the view will “react”, updating to match the new values.
When this data changes, the view will re-render. It should be noted that properties in
data are only reactive if they existed when the instance was created. That means if you add a new property, like:
Then changes to
b will not trigger any view updates. If you know you’ll need a property later, but it starts out empty or non-existent, you’ll need to set some initial value. For example:
The only exception to this being the use of
Object.freeze(), which prevents existing properties from being changed, which also means the reactivity system can’t track changes.
In addition to data properties, Vue instances expose a number of useful instance properties and methods. These are prefixed with
$ to differentiate them from user-defined properties. For example:
In the future, you can consult the API reference for a full list of instance properties and methods.
Each Vue instance goes through a series of initialization steps when it’s created - for example, it needs to set up data observation, compile the template, mount the instance to the DOM, and update the DOM when data changes. Along the way, it also runs functions called lifecycle hooks, giving users the opportunity to add their own code at specific stages.
For example, the
created hook can be used to run code after an instance is created:
There are also other hooks which will be called at different stages of the instance’s lifecycle, such as
destroyed. All lifecycle hooks are called with their
this context pointing to the Vue instance invoking it.
Don’t use arrow functions on an options property or callback, such as
created: () => console.log(this.a) or
vm.$watch('a', newValue => this.myMethod()). Since an arrow function doesn’t have a
this will be treated as any other variable and lexically looked up through parent scopes until found, often resulting in errors such as
Uncaught TypeError: Cannot read property of undefined or
Uncaught TypeError: this.myMethod is not a function.
Below is a diagram for the instance lifecycle. You don’t need to fully understand everything going on right now, but as you learn and build more, it will be a useful reference.