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)

Benefits of using Flux

The following are some of the benefits that Facebook gained after introducing Flux to their web applications:

  • Better scalability than the classic MVC
  • Easy-to-understand data flow
  • Easier and more effective unit tests
  • Since actions represent behaviors of the application, behavior-driven development is a perfect match to write applications using Flux architecture

By adding the Vuex framework to your Vue.js application, you will experience the same benefits. In addition, Vuex, like Redux, simplified this architecture in several different ways, such as using a single store per application and removing the dispatcher from the process in favor of using the store to dispatch actions.