This content originally appeared on DEV Community and was authored by Ahmad Alhafi
Sure, it’s a bit rudimentary, but honestly, I like it 🪵
Alright, let’s dive into the core types of Signals in their first version, v16:
🎗 signal()
Stores a reactive, writable value.
A bit funny when we mix Arabic terms with programming, but here’s the explanation:
It’s a value you can store and update, and it’s reactive—so whenever it changes, anywhere you use it (in HTML or code) updates automatically.
You can update the value in two ways:
signal.update() → modifies the value based on the previous value
signal.set() → sets a new value directly, without relying on the old value
🎗 computed()
A value derived from an existing signal, reactive but read-only.
It depends on other signals in your code and cannot be modified directly using set() or update().
You can use it just like a signal, both in templates and in code.
🎗 effect()
Executes a side effect whenever a dependent signal changes.
For example, in the image, when the count signal changes, it automatically logs a value to the console.
Important note: In v16, Signals are still in Developer Preview / PoC stage.
That means it’s proof that the solution works and can solve specific problems, but we’re still using zone.js under the hood.
And that’s it!
If you’re still unclear about how it works, check out this post:
https://lnkd.in/dvFG2P3d
This content originally appeared on DEV Community and was authored by Ahmad Alhafi
Ahmad Alhafi | Sciencx (2025-08-26T19:37:31+00:00) Signals in Angular 16, Signals beginning. Retrieved from https://www.scien.cx/2025/08/26/signals-in-angular-16-signals-beginning/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.