Version Details and Security Vulnerabilities

📦

@angular/common

17.3.2

Comparision Betweeen 17.3.2 and 17.3.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

3016

3015

Unpacked Size

10.88 MB

10.87 MB

Version 17.3.2 Details

Angular developers considering an update to @angular/common from version 17.3.1 to 17.3.2 will find a relatively incremental change, primarily focused on bug fixes and minor improvements, rather than a sweeping overhaul of features. Both versions share the same fundamental description, providing essential directives and services for Angular applications. They both depend on tslib version ^2.3.0 for TypeScript helper functions and maintain compatibility with rxjs versions ^6.5.3 || ^7.4.0 and @angular/core versions corresponding to their own release (17.3.1 and 17.3.2 respectively) demonstrating a commitment to maintaining existing rxjs and core functionalities. The license remains MIT, ensuring developers can freely use and modify the package.

The primary difference lies in the updated build, reflected in the dist object. Version 17.3.2 has a slightly larger unpacked size (11408217 bytes versus 11396708 bytes) and an additional file compared to the previous version, suggesting the inclusion of either new assets, refined implementations or potentially some fixes related to internationalization directly integrated by the Angular team. The releaseDate also indicates a more recent build, meaning the newer version contains the latest fixes and enhancements made available for @angular/common. So upgrading from 17.3.1 is a simple and recommended procedure to get the last bug fixes and internal improvement.

While the core API and functionality remain consistent across versions, developers should review the official Angular changelog and release notes for @angular/common version 17.3.2 to identify the specific bug fixes and enhancements included. This will ensure that the update addresses any known issues affecting their projects and allows them to benefit from the latest stability improvements.

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.