What this book covers

Managing state transitions is one of the hardest parts of building applications. This is especially true on the web, where you also need to ensure that the state is reflected in the URL. In addition, we often want to split applications into multiple bundles and load them on demand. Doing this transparently is not trivial.

The Angular router solves these problems. Using the router, you can declaratively specify application states, manage state transitions while taking care of the URL, and load bundles on demand.

In this book, I will talk about the router's mental model, its API, and the design principles behind it. To make one thing clear: this book is not about Angular. There is a lot of information about the framework available online. So if you want to get familiar with the framework first, I would recommend the following resources:

•   angular.io : It's the best place to get started
•   egghead.io : The Angular Fundamentals on egghead.io is an excellent way to get started for those who learn better by watching
• vsavkin.com : My blog contains many articles where I write about Angular in depth

Therefore in this book, I assume you are familiar with Angular, and so I won't talk about dependency injection, components, or bindings. I will only talk about the router.