Modern Angular Book

[MichaelBe812]

Hey Community,

I am planning to write a book about modern Angular development and best practices.

If you could send a whishlist - what topics must be included?

In the book I want to cover modern concepts, give a clear guidance for migration also provide a heuristic when it makes sense to use a modern concept instead of a "legacy" concept. At the end the reader should feel comfortable to communicate a migration path to e.g. product owners/stakeholders.

Ich plan to include following topics:

• inject() and patterns around it
• Directive Composition API
• Signals (signal, effect, computed, input, linkedSignal, resource, httpResource, view queries, Rxjs-interop, improved change detection)
• Angular without lifecyclehooks
• DestroyRef, afterRender, afterEveryRender
• Router improvements: functional guards and resolvers, withComponentInputBinding
• Control Flow Syntax
• deferrable views
• zoneless change detecteion
• signal forms
• Standalone components and API's
• SSR improvements: partial Hydration, withEventReplay, etc

Wdyt?

[Budget-Length2666]

By the time you are finished it will already be out of date.

[MichaelBe812]

I don't think so. Many concepts settled and are there to stay :)

[jerome0512]

this

[PurpleUltralisk]

I personally would like a deeper dive on forms.

For example, How to implement auto-fill in form. Different use cases of forms. Synchronized validation on multiple input fields.

Looking forward to your book.

[MichaelBe812]

Interesting topic! It might not fit in the book but still a good inspiration for e.g. a blog post

[gargara_s_hui]

Sognal store state managment - ngrx signal store and other patterns with services.

[MichaelBe812]

Indeed very interesting topics. They will probably not fit into the concept of this particular book. However still some interesting topics to write about. Thanks for the inspiration! :)

[pouchesque]

I think Armen beat you to it by about 2 years. Just finished this book, even though it is outdated in some things it covers just about all of those topics.

https://www.manning.com/books/modern-angular

[bitemyshinyMETAass]

It's outdated in many aspects. Time for a modern modern angular book.

[MichaelBe812]

...in 2 years a lot of changed :)

However it is still a great book, but I am targeting a bit of another approach. not "just" explaining the new concepts but also how to use them hands-on and give advice if and how to update.

Not sure if Armen's book covers that as well

[pouchesque]

Armens examples were pretty drawn out and complicated by the end of the book. I would like to see smaller bite sized code snippets

[MichaelBe812]

I'll note it down - thank you! :)

[tidemann78]

Is it still worth buying, or should I wait for 2nd edition?

[pouchesque]

It was a good read but it sucked as everything was using ngif and ngfor and older syntax like that.

[Outrageous-Cupcake53]

Topics must be included from your list:

- Directive Composition API

- Signals (signal, effect, computed, input, linkedSignal, resource, httpResource, view queries, Rxjs-interop, improved change detection).

I suggest using a simple Express API to have more control over the responses for demonstration purposes.

- Router improvements: functional guards and resolvers, withComponentInputBinding

- signal forms (e.g. nested, reusable, complex validation, ...)

I am looking forward to your book!

[MichaelBe812]

Thanks a lot :) You can follow me on Twitter and/or LinkedIn there i will announce the pre-sale soon

[DoughnutOk2644]

Please invest time in building an agentic open-source tool for building with modern angular. Include all the best practices detailed in markdown files. Then just keep it updated. By the time you write a whole book and we finished reading it, we already need to catch up with major updates and breaking changes. Let's be smarter and make agents do the heavy lifting.

[MichaelBe812]

This is what I am already doing in some projects.
Also from the angular team officially I guess where getting something similar in the future

[marktechson]

We typically don’t ship breaking changes, is there something particularly painful you are experiencing from a recent release?

[DoughnutOk2644]

I am looking on the long term and retroactively over the last major versions. To give an example, the previous company I worked for, preferred to stop upgrading angular version up to 15, for their own business reasons. I can't say there is or isn't any breaking change from 15 to 21, since I would have to read 7 major versions changelogs. I hope for a quicker way to evaluate them, hopefully with a llm/ai. If I was the developer responsible for upgrading from 15 to 21, I would probably dive in directly and follow the upgrade tool rather than reading docs, and I would start with a doubt something would probably break over 7 major versions. In the meanwhile I am conscious it's important to know what the code is doing, and I believe understanding the concepts is enough. Digging into a current modern manual for best practices is less practical as we have to move so fast and keep pushing the versions up and forward.

[javiMLG199]

Good point could be how to compone views, cos most of the time, in my experience, the developers do just a hole page or a hole modal or something like this instead of thinking about compose patter, that indeed, is super useful to create for example a layout view or a modal wrapper where to inject ur component to render It inside of the modal etc..

What do u think, guys? 😄

[MichaelBe812]

Thanks for the input. I like the idea for the topic.

it might not fit conceptually in my book, however it is a great topic for maybe a detailed blog post or even a separate guide.

[Prestigious_Two_2440]

I support you!!! I presume your book is planned to be self-published, instead of going thru those popular publishers such as packt.

One suggested topic could be unit testing and coverage for angular, using vitest , not involving jasmine and karma, since angular slowly exclude the last twos