You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/astro-docs/src/content/docs/blog/v3.mdx
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,13 @@ Angular Three v3 is here with Angular 19 support! 🎉
24
24
25
25
Angular Three v3 drops support for Angular 18 and below. This is because Angular 19 comes with a huge change
26
26
to the Effect API (Learn more [here](https://riegler.fr/blog/2024-10-15-effect-context/)). While nothing really changes much to consumers,
27
-
the way Angular Three utilizes the Effect API changes.
27
+
the way Angular Three utilizes the Effect API changes. From the library perspective, this update also allows for Angular Three components to go `standalone` by default.
28
28
29
-
From the library perspective, this update also allows for Angular Three components to go `standalone` by default.
29
+
That said, there are several benefits of Angular 19 to Angular Three, and its consumers:
30
+
31
+
- Lighter effects with less microtasks; One of the changes to the new Effect API is that a certain type of effects is scheduled in a smarter way instead of _microtask-ing_ everything.
32
+
- Faster execution in some areas; Another change to the new Effect API is that setting signals inside of effects is now allowed. Hence, `untracked` trick or `allowSignalWrites` is no longer needed.
33
+
- Decreased library size; With default `standalone: true` and static analysis on `imports` array, Angular Three v3 is able to shed some of its bundle size.
0 commit comments