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

Continuous Integration (CI)


There are a variety of CI platforms available, such as Travis, GitLab, Jenkins, and countless others. Each platform often serves a common goal, that is, automating deployment and the challenges that come along with it.

Sure, we could deploy our site, run our tests, and continue with other items in our forever increasing build steps. Not only is this a tedious process, but it also gives us many opportunities to make mistakes. Furthermore, it also means that each step has to be documented for every member of the team, the documentation has to be kept up to date and is not exactly scalable across an organization.

For our examples, we'll be using Travis CI, and the first objective that I'd like to tackle is automatically running our unit tests. To do this, we'll need one or more unit tests inside of our project.

Unit tests

We covered testing our Vue.js applications in the preceding chapter, so wouldn't it be nice to automatically run our tests each time we push a new...