Book Image

Vuex Quick Start Guide

By : Andrea Koutifaris
Book Image

Vuex Quick Start Guide

By: Andrea Koutifaris

Overview of this book

State management preserves the state of controls in a user interface. Vuex is a state management tool for Vue.js that makes the architecture easier to understand, maintain and evolve. This book is the easiest way to get started with Vuex to improve your Vue.js application architecture and overall user experience. Our book begins by explaining the problem that Vuex solves, and how it helps your applications. You will learn about the Vuex core concepts, including the Vuex store, changing application state, carrying out asynchronous operations and persisting state changes, all with an eye to scalability. You will learn how to test Vuex elements and Vue components with the Karma and Jasmine testing frameworks. You will see this in the context of a testing first approach, following the fundamentals of Test Driven Development. TDD will help you to identify which components need testing and how to test them. You will build a full Vuex application by creating the application components and services, and persist the state. Vuex comes with a plugin system that allows programmers to extend Vuex features. You will learn about some of the most powerful plugins, and make use of the built-in logger plugin. You write a custom Google Analytics plugin to send actions to its analytics API, and an Undo/Redo plugin.
Table of Contents (8 chapters)

Understanding the core concepts of Vuex

It is now time to introduce the Vuex architecture, which consists of five core concepts:

  • Single state tree
  • Getters
  • Mutations
  • Actions
  • Modules

Each concept will be discussed in detail, with some pieces of code that will help to make it clear. Once you have read the following pages, you will have a clear understanding of Vuex architecture.

Understanding the Vuex store

Vuex implements Flux stores using a single state tree. In this, it differs from Flux because in Flux there could be more than one store. You may think that a single store/state is not good for modularity. Later, we will see how to split the single state tree into modules.

Having only one store has some benefits:

  • It is available...