Assuming main app is Angular, instead of AngularJS

[aaronfrost]

As I read this book the first time, I had no actual practical experience, so it was all very informational and helpful. Then I started to implement it, and I noticed something: Most of the documentation and examples assume that a person who is upgrading from AngularJS to Angular will have a main app in Angular. That is not going to be the case, most of the time, IMO. On day one, when someone begins to upgrade from AngularJS to Angular, 100% of their code will be in AngularJS. Neither their main app or their lazy loaded bundles will contain any Angular code. While all of the examples provided in the book are extremely helpful, they would be even more so if they assumed that most of us will be starting in an all AngularJS world, and not in an all Angular world, and adding in bits of AngularJS via lazy loading.

If this book approached the problem like many of us are going to, from an AngularJS-first approach, it would make it much easier to implement.

My 2cents. Sorry for being critical. This book has been my trustworthy anchor. I have depended on it heavily and it has gotten me through a lot of my questions. But I keep running into dead ends that the book doesn't help me with because it is written from an Angular-first POV.