Angular Version Compatibility for Syncfusion^® Components

22 Jun 20253 minutes to read

Supported Angular Versions

The following table outlines the compatibility between Syncfusion^® Angular UI components and supported Angular versions:

Angular Version	Compatible Syncfusion^® Angular Components Version
Angular v19	26.1.35 and above
Angular v18	25.2.3 and above
Angular v17	23.2.4 and above
Angular v16	21.1.39 and above
Angular v15	20.4.38 and above
Angular v14	20.2.36 and above
Angular v13	19.4.38 and above
Angular v12	19.3.43 and above

Ivy and Non-Ivy Package Compatibility

Starting from version 20.2.36, Syncfusion^® Angular packages are compatible with the Angular Ivy compiler. However, to support both Ivy and non-Ivy (View Engine) applications, Syncfusion^® provides two different package distributions:

Ivy-compatible packages: These are the default packages and do not require any special suffix.
Non-Ivy (View Engine) packages: For applications still using the View Engine, append the -ngcc suffix to the package version in the package.json file.

Usage of ngcc Packages

The Angular Compatibility Compiler (ngcc) is used to make non-Ivy packages compatible with Ivy-based applications. For Syncfusion^® components, use the following guidelines:

For Ivy-based applications (Angular 12 and above): Use the default packages without any suffix.

Example:
```
"@syncfusion/ej2-angular-grids": "20.2.38"
```
For non-Ivy applications (using View Engine): Add the -ngcc suffix to the package version.

Example:
```
"@syncfusion/ej2-angular-grids": "20.2.38-ngcc"
```

Note: The -ngcc suffix is only required for versions 20.2.36 and later when using non-Ivy applications. For Ivy-based applications, which is the default for Angular 12 and above, use the packages without the suffix.

For detailed installation instructions, refer to the Angular package installation guide.

Understanding Syncfusion^® Version Numbers

Syncfusion^® follows a quarterly release cycle for major updates. The version numbering system for Syncfusion Angular components uses semantic versioning in the format Major.Minor.Patch. This system allows developers to quickly understand the nature of each release.

For example, a release version 22.1.34 can be interpreted as follows:

22 - Major version (updated quarterly)
This number represents significant updates to the library. It may include major enhancements, new features, bug fixes, and potential breaking changes. Syncfusion^® increments this number every three months as part of their quarterly release cycle.

1 - Minor version
The minor version indicates the release of new features and bug fixes that maintain backward compatibility. When Syncfusion^® adds functionality in a backwards-compatible manner, they increment this number.

34 - Patch version
This number is incremented for weekly patch releases. These releases primarily consist of bug fixes and minor improvements that do not introduce new features or breaking changes.

By understanding this versioning system, developers can easily assess the impact and nature of each Syncfusion^® update, helping them make informed decisions about when to upgrade their applications.

Staying Up-to-Date

To ensure optimal performance and access to the latest features, it’s recommended to keep Syncfusion^® Angular components updated to the most recent version compatible with the Angular version in use. Regular updates provide:

Access to new features and improvements
Enhanced performance and stability
Timely bug fixes and security patches

Angular Version Compatibility for Syncfusion® Components