Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Vue.js 3 Design Patterns and Best Practices
  • Table Of Contents Toc
  • Feedback & Rating feedback
Vue.js 3 Design Patterns and Best Practices

Vue.js 3 Design Patterns and Best Practices

By : Pablo David Garaguso
4.8 (10)
close
close
Vue.js 3 Design Patterns and Best Practices

Vue.js 3 Design Patterns and Best Practices

4.8 (10)
By: Pablo David Garaguso

Overview of this book

If you’re familiar with the progressive Vue framework for creating responsive user interfaces, you’ll be impressed with its latest iteration, Vue 3, which introduces new concepts and approaches design patterns that are uncommon in other libraries or frameworks. By building on your foundational knowledge of Vue 3 and software engineering principles, this book will enable you to evaluate the trade-offs of different approaches to building robust applications. This book covers Vue 3 from the basics, including components and directives, and progressively moves on to more advanced topics such as routing, state management, web workers, and offline storage. Starting with a simple page, you’ll gradually build a fully functional multithreaded, offline, and installable progressive web application. By the time you finish reading this Vue book, not only will you have learned how to build applications, but you’ll also understand how to solve common problems efficiently by applying existing design patterns. With this knowledge, you’ll avoid reinventing the wheel for every project, saving time and creating software that’s adaptable to future changes.
Table of Contents (16 chapters)
close
close

Coverage

The concept of coverage is very simple, and it answers the question of how much of our code is covered by automated tests. We know that 100% coverage is only possible for small applications, as the same effort for large projects falls fast into the law of diminishing returns Vitest offers us a simple way to answer this question by running the vitest –coverage command. In our case, we have already set this option in our package.json scripts section, so we can run the following command:

$ npm run test:coverage

When the preceding command is run, if any dependency is missing, it will prompt us on whether we want to try to download and install it:

Figure 9.3 – Vitest prompts us to install missing dependencies for coverage

Figure 9.3 – Vitest prompts us to install missing dependencies for coverage

For our chapter code example, the coverage report should look something like this:

Figure 9.4 – Vitest coverage report example

Figure 9.4 – Vitest coverage report example

It is possible to retrieve this information on...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY