Version Details and Security Vulnerabilities

📦

@angular/common

19.0.6

Comparision Betweeen 19.0.6 and 19.0.5

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

2903

Unpacked Size

9.06 MB

Version 19.0.6 Details

Angular developers will find subtle but potentially important distinctions between @angular/common versions 19.0.6 and 19.0.5. Both packages provide essential directives and services for Angular applications, sharing the same core description, license (MIT), and repository details. The dependency on tslib remains consistent at ^2.3.0. Peer dependencies also stay aligned, requiring compatible versions of rxjs (^6.5.3 || ^7.4.0) and @angular/core.

The primary differences lie in the versioning of its peer dependency @angular/core and the releaseDate property. Version 19.0.6 has a peer dependency on @angular/core with also the version 19.0.6 being the peer dependency version, showing that it will require this version to work properly. This constraint suggests that upgrading to @angular/common@19.0.6 necessitates upgrading to @angular/core@19.0.6 to ensure compatibility. This coupling is important for preventing unexpected errors or breaks. Version 19.0.5 requires the peer dependency @angular/core with version 19.0.5.

Another key difference is the release date. Version 19.0.6 was released on 2025-01-08T18:05:01.079Z, while version 19.0.5 was released on 2024-12-18T18:57:43.419Z. This implies that version 19.0.6 includes bug fixes, minor enhancements, or security patches implemented after the release of 19.0.5. The unpackedSize is almost identical (9496384 vs 9496383), suggesting that the added changes were small. Developers should review the Angular changelog for a full understanding of the implemented changes. Before updating, developers should test these changes in their development environment to ensure a smooth transition and prevent unforeseen issues.

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.