Damiano Fusco - Large Scale Apps with Vue 3 and TypeScript

First, I would like to thank Evan You. Thank you for not giving up on this project a few years ago when it was still small and people were still skeptical about it. You gave us an amazing gift with such a lightweight and performing framework, which is progressive and not opinionated like many others out there.

I also want to thank my son for helping me proof read and validate the steps in each chapter by building the same project.

I want to thank my wife Paola for translating the first 5 chapters of the Italian edition, Stefano Rampazzo for translating the resto of the chapters of the Italian edition, Alexey Pyltsyn for translating the Russian edition, and Victor Borrs Castell for translating the Spanish edition.

The audience for this book is from beginners with some experience in MV* applications, to advanced developers. The format is similar to a cookbook, but instead of individual recipes well go through creating a project and keep enhancing, refactoring, and make it better as we move forward to more advanced chapters to show different patterns, architecture, technologies.

Note: Some of the patterns illustrated here are not specific to Vue, but can applied in any application written in TypeScript or JavaScript. For example, code from Chapters 3, 7, 8, 14 can also be used in React/Angular or other front-end apps. Similarly, code from Chapters 3 and 14 can also be used in NodeJS apps.

The primary goal of this book is to show you how to structure a Vue.js project, its directories and files, adopt naming conventions, follow state management patterns, enforce type checking at development time through TypeScript, write unit tests, and more, in proven ways that offer a solid foundation for building a large-scale application that is more easily to expand and maintain.

Well start creating a simple project and grow this throughout the chapters to show how some patterns, naming conventions, and strategies, will help create a more solid foundation and keeping the code organized and avoid cluttering.

Well create a TypeScript API client that can easily serve static mocked data or switch to communicate with a live API once that is available, thus enabling to develop our front-end early even before we (or another team) has completed their back-end coding for the API. Well integrate internationalization and localization, learn how we can create plugins, and more.

IMPORTANT: We will initially write code that allows us to achieve the desired functionality quickly, even if it requires more code, but then we constantly rework it (refactoring) to improve it and find solutions that allow us to reduce the amount of code used, or to organize it in a clear and easy way to is easy to expand and maintain. So arm yourself with a lot of patience!

Going forward, I would refer to Vue.js simply with Vue. I will highlight most terms or names in bold, rather than define different fonts/styles depending on whether a term is code, or a directory name or something else.