Book Image

Vue.js 3 By Example

By : John Au-Yeung
Book Image

Vue.js 3 By Example

By: John Au-Yeung

Overview of this book

With its huge ecosystem and wide adoption, Vue is one of the leading frameworks thanks to its ease of use when developing applications. However, it can get challenging for aspiring Vue.js developers to make sense of the ecosystem and build meaningful applications. This book will help you understand how you can leverage Vue effectively to develop impressive apps quickly using its latest version – Vue 3.0. The book takes an example-based approach to help you get to grips with the basics of Vue 3 and create a simple application by exploring features such as components and directives. You'll then enhance your app building skills by learning how to test the app with Jest and Vue Test Utils. As you advance, you'll understand how to write non-web apps with Vue 3, create cross-platform desktop apps with the Electron plugin, and build a multi-purpose mobile app with Vue and Ionic. You'll also be able to develop web apps with Vue 3 that interact well with GraphQL APIs. Finally, you'll build a chat app that performs real-time communication using Vue 3 and Laravel. By the end of this Vue.js book, you'll have developed the skills you need to build real-world apps using Vue 3 by working through a range of projects.
Table of Contents (10 chapters)

Understanding components

Components can only have so much inside them. They take props from the parent component, so we can customize their behavior. Additionally, they can have computed properties and watchers to watch for reactive properties and return the data or do the things we want them to do. They can also have methods that allow us to do specific things with them. Components should be simple; that is, they should not have too much going on inside them. Templates should only have a few elements and components inside them in order to keep them simple. Components also have some built-in directives for us to manipulate the Document Object Model (DOM) and carry out data binding.

Other than that, components cannot do much. It would be impossible to build anything with non-trivial complexity if we only have a few components and no way to navigate with URLs.

If our app only has components, then we can only nest a few of them before it gets too complex. Additionally, if we have...