Book Image

Angular Projects

By : Zama Khan Mohammed
Book Image

Angular Projects

By: Zama Khan Mohammed

Overview of this book

<p>Angular is one of the best frameworks, not only for building web applications, but also for building applications on other platforms such as desktop and mobile. It is packed with amazing web tools that allow developers to become more productive and make the development experience a happier one </p><p>This book will be your practical guide when it comes to building optimized web apps using Angular. The book explores a number of popular features, including the experimental Ivy rendered, lazy loading, and differential loading, among others, in the projects. It starts with the basics of Angular and its tools, which will help you to develop and debug Angular applications. You will learn how to create an SPA using Angular Router, and optimize it by code splitting and Preloading Routes. We will then build a form-heavy application and make forms reactive by using Reactive Forms. After that, we will learn how to build a Progressive Web App, and a server-side rendering app, as well as a MonoRepo app. Furthermore, we will also dive into building mobile apps using Ionic and NativeScript. Finally, we end the book by creating a component library for our application using Angular CDK and then testing it. </p><p>By the end of this book, you’ll have gained comprehensive insights into using Angular, along with hands-on experience in creating intuitive real-world applications.</p>
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
Foreword

Exploring the monorepo application

In our organizations, we typically have multiple applications, from backend applications to multiple frontend applications, and all of them have their own repository where the code resides. Each team that develops a particular application deals with multiple repositories related to that project. In such projects, it's really difficult to share common code between multiple applications and manage their dependencies. 

One way to solve this is by using just one repository for all the applications. However, this kind of setup will be complicated to manage. Building anything in such an environment is difficult, as any changes we make mean that we have to build all the applications again, which increases the build time significantly. To solve this, we just need to build the applications that are affected by the changes, rather than building...