Book Image

Vue.js 2 Design Patterns and Best Practices

By : Paul Halliday
Book Image

Vue.js 2 Design Patterns and Best Practices

By: Paul Halliday

Overview of this book

Vue.js 2 Design Patterns and Best Practices starts by comparing Vue.js with other frameworks and setting up the development environment for your application, and gradually moves on to writing and styling clean, maintainable, and reusable Vue.js components that can be used across your application. Further on, you'll look at common UI patterns, Vue form submission, and various modifiers such as lazy binding, number typecasting, and string trimming to create better UIs. You will also explore best practices for integrating HTTP into Vue.js applications to create an application with dynamic data. Routing is a vitally important part of any SPA, so you will focus on the vue-router and explore routing a user between multiple pages. Next, you'll also explore state management with Vuex, write testable code for your application, and create performant, server-side rendered applications with Nuxt. Toward the end, we'll look at common antipatterns to avoid, saving you from a lot of trial and error and development headaches. By the end of this book, you'll be on your way to becoming an expert Vue developer who can leverage design patterns to efficiently architect the design of your application and write clean and maintainable code.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Free Chapter
1
Vue.js Principles and Comparisons
12
Server-Side Rendering with Nuxt
Index

What is Vuex?


State management is an important part of modern-day web applications, and managing this state as the application grows is a problem every project faces. Vuex looks to help us achieve better state management by enforcing a centralized store, essentially a single source of truth within our application. It follows design principles similar to that of Flux and Redux and also integrates with the official Vue devtools for a great development experience.

So far, I've spoken aboutstateandmanaging state, but you may still be confused as to what this really means for your application. Let's define these terms in a little more depth.

State Management Pattern (SMP)

We can define a state as the current value(s) of a variable/object within our component or application. If we think about our functions as simple INPUT -> OUTPUT machines, the values stored outside of these functions make up the current condition (state) of our application.

Note how I've made a distinction between component level...