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

Chapter 13. Patterns

In this chapter, we'll look at a variety of anti-patterns within Vue.js and review concepts at a high level that we've learned throughout the book. We'll look at various patterns and anti-patterns and how we can write code that is consistent across teams and your own projects.

Before defining anything as a pattern or anti-pattern, it's important to accurately define both for the reader. If something is to be considered a pattern, this means that this is a recommended practice in the vast majority of cases. On the contrary, if I've defined it as an anti-pattern, then it's most likely not a recommended practice in a vast majority of cases. For further information on this, a good source of patterns and guidelines can be found at https://github.com/pablohpsilva/vuejs-component-style-guide.

Software development is an opinionated field with a variety of ways to solve the same problem, so there may be ideologies that are classified as something you don't agree with, and that...