Introducing Angular Ivy to jQWidgets
Starting with Angular version 8, you can choose to opt in to start using a preview version of Ivy and help in its continuing development and tuning. More about Ivy: https://angular.io/guide/ivy.
Ivy is smaller, faster, and simpler. It will become the default engine in Angular 9.
Angular Ivy includes two key concepts: Locality and Tree-shaking.
Locality and Tree-shakingLocality means that Ivy compiles one file at a time. It only looks at a component and its template, not its dependencies, when generating the output. Tree-shaking means that, if you are not using something in Angular, it does not get included.
What Ivy Means to all Angular application developersBy using Angular Ivy, the benefits are:
- 1. Better build times (with a more incremental compilation)
- 2. Better build sizes (with a generated code more compatible with tree-shaking)
- 3. Unlocks new potential features (metaprogramming or higher order components, lazy loading of component instead of modules, a new change detection system not based on zone.js…)
- 4. Human Readable Code
- 5. Faster Development
The Good News about jQWidgets & Angular IvyWe are very happy to share that jQWidgets Angular Components are now fully compatible and tested with the Angular Ivy Engine. Now you can build your apps with the latest and biggest feature of Angular and take use of all of its advantages. You may take a look at: jqwidgets-ng
We do not have to change how we write our applications.
Angular Ivy View Engine aims to be compatible with the existing applications,
so we will just need to turn it on, no changes to the code needed.