Version Details and Security Vulnerabilities

📦

@angular/common

17.1.2

Comparision Betweeen 17.1.2 and 17.1.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

3011

Unpacked Size

10.69 MB

10.65 MB

Version 17.1.2 Details

Angular's @angular/common package, a cornerstone for Angular applications providing essential directives and services, saw a recent update from version 17.1.1 to 17.1.2. Both versions maintain the same core description and MIT license, ensuring continued stability and freedom for developers. Crucially, both rely on tslib version ^2.3.0 for TypeScript helpers and share peer dependencies on rxjs (^6.5.3 || ^7.4.0) and @angular/core. This means existing projects using compatible versions of RxJS and Angular core should experience seamless updates.

While the dependency structure remains consistent, the updated version 17.1.2 includes enhancements and bug fixes reflected in its increased unpacked size of 11,206,235 bytes compared to 17.1.1's 11,170,760 bytes. The file count remains the same at 3011, indicating that the update likely involves modifications to existing files rather than the addition of new ones. Developers should note the release date difference: version 17.1.2 was released on January 31, 2024, following version 17.1.1's release on January 24, 2024. This quick turnaround suggests that 17.1.2 addresses any urgent issues discovered shortly after the release of 17.1.1. Developers seeking the most stable and up-to-date experience are encouraged to upgrade to version 17.1.2 to benefit from these improvements and bug fixes within the Angular common module. Review the official Angular changelog for a comprehensive list of specific changes.

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.