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)

Connecting the frontend and the backend

To make the frontend app communicate with the backend app, we'll need to enable cross-domain communication on the backend so that the traffic from the frontend can go through to the backend. This can easily be done with the Cross-Origin Resource Sharing (CORS) middleware that we will add to our Express app.

To work with SQLite databases, we use the sqlite3 library, which lets us manipulate the SQLite database within the Node.js apps. We can make queries and run SQL commands to insert or remove data from our database.

Additionally, we will have simple authentication for the admin frontend. We will check the username and password for the admin login, and if it's valid, we can issue a token and send it to the frontend. Then, the frontend will use the token, which is stored in the header, to check whether the request can be made from the frontend. We add authentication for the admin-only routes only, so we only need to check the token...