Version Details and Security Vulnerabilities

📦

@angular/compiler

19.1.3

Comparision Betweeen 19.1.3 and 19.1.2

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

4.07 MB

Version 19.1.3 Details

Angular developers will find subtle but potentially impactful differences between @angular/compiler versions 19.1.3 and 19.1.2. Both versions share the same core description as the Angular compiler library, licensed under MIT and maintained within the Angular project on GitHub. They both depend on tslib version 2.3.0 or higher. The crucial peer dependency, @angular/core, is aligned perfectly with @angular/compiler version, indicating that 19.1.3 of @angular/compiler should be used with 19.1.3 of @angular/core and 19.1.2 of @angular/compiler should be used with 19.1.2 of @angular/core.

A primary distinction lies in the dist data. Version 19.1.3, released on January 22, 2025, has an unpacked size of 4,272,147 bytes, slightly larger than version 19.1.2 (released January 20, 2025), which has an unpacked size of 4,268,480 bytes. This suggests that version 19.1.3 includes minor additions, bug fixes, or performance enhancements absent in 19.1.2. While the file count remains consistent at 6, the increase in unpacked size means a larger code base.

Developers should prioritize upgrading to version 19.1.3 to leverage the included improvements and bug fixes and ensure compatibility with @angular/core@19.1.3. Although the changes are relatively small, staying current with the latest patch releases is good practice for optimal stability and performance within Angular applications. The two-day difference in release date suggests that the latter version fixes issues discovered in or shortly after the release of the earlier version.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.