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

What is source control... and why?

Software development is a “human-intensive” discipline, meaning that it depends heavily on the creativity and involvement of the developer and their know-how. It is common to try different approaches to the same situation and write and rewrite code. Even the process of refactoring after testing implies making changes in the code. It is not an anomaly that during this process, we need to “go back” to a previous code when a change or approach didn’t meet expectations. If we are constantly overwriting the same files... how do we keep track of what changed where? And by whom? Our own memory is not enough when time and complexity grow. Save files with different names? That would become impractical very soon. And what about combining source code from multiple developers? We can quickly see that managing the source code for non-trivial projects is a very important task in itself.

The historical solution to this early...

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