This little explainer serves as a visual explainer for some of the concepts Angular is interested in discussing with the introduction of Signals-based reactivity. Though Signals are not a new concept in the framework space, these differ radically both in terms of public API as well as behavioral details (such as eager vs lazy computation, batching behavior, equality, cleanup, nesting, etc).
Demo site: https://angular-signals.netlify.app/
If you're interested in being part of the discussion, please join us in our discussion space for our RFC!
And here is a stackblitz that allows you to play around with this initial version, compliments to Enea Jahollari.
This project was generated with Angular CLI version 14.0.0-rc.2.
Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.