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

Why testing?


Automated testing tools exist for a reason. When it comes to testing the work that we've created manually, you'll know from experience that this is a long, (sometimes complex) process that does not allow for consistent results. Not only do we have to manually remember whether a particular component works (or otherwise write the results down somewhere!), but it isn't resilient to change.

Here are some phrases I've heard over the years when testing has been brought up:

"But Paul, if I write tests for my application it'll take three times as long!"

"I don't know how to write tests..."

"That's not my job!"

...and a variety of others.

The point is that testing is a skill in the same sense that development is a skill. You may not be immediately great at one or the other, but with time, practice, and perseverance, you should find yourself in a position where testing feels natural and a normal part of software development.