Andrew Scott from the Angular team discussed Angular without zone.js. Various content authors published videos about topics like Signals for forms.
Andrew Scott on zoneless
TechStackNation runs sessions with members of the Angular team quite often. This time, it was Andrew Scott, and the discussion evolved around removing zone.js, which landed in Angular 18 in an experimental mode. Zone.js triggers the change detection where Angular updates the DOM.
Andrew told us a little about the trade-offs. On the one hand, zone.js does everything for us in terms of change detection and is reliable. On the other hand, it could be more performant. Signals are a very good fit here because they can trigger Change Detection and point it to the right components.
Some might ask if Signals should always be used when representing values in a template. We got a very clear answer.
Andrew also touched on zoneless testing. We should use the whenStable() function of the ComponentFixture and not rely on zone-based functions like fakeAsync().
Another discussed topic was the relationship between the Angular and the TypeScript language server.
Misc. Content
Other than that, we got new videos from various content authors.
Glitch-Free and toObservable()
Angular University explained the Signal's glitch-free effect and fixed a misunderstanding that toObservable could work around it.
Dynamic Form Validators
Dmytro Mezhenskyi, aka. Decoded Frontend, showed how to dynamically add but also remove validators from a form and what kind of pitfalls we have to be aware of.
Conflict Management in NPM
For those who constantly run into npm issues and are required to use force or with-legacy-peers, Francesco Borzi has an alternative that uses the override property in the package.json
How to avoid using “force” and “legacy-peer-deps” when running npm install/ci | by Francesco Borzì | JavaScript in Plain English
Learn a better alternative to deal with one of the most common errors of npm install.
javascript.plainenglish.io
Top comments (0)