Version Details and Security Vulnerabilities

📦

@angular/common

8.0.2

Comparision Betweeen 8.0.2 and 8.0.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

2338

Unpacked Size

13.61 MB

Version 8.0.2 Details

Angular developers looking to leverage common directives and services within their applications should pay attention to the nuances between @angular/common versions 8.0.1 and 8.0.2. Both versions, built upon the foundation of the Angular framework, share identical file counts (2338) and unpacked sizes (14270642), suggesting minimal underlying code changes. They depend on tslib version ^1.9.0 and require peer dependencies of rxjs ^6.4.0 along with a matching @angular/core version.

The key differentiator lies in the specific @angular/core peer dependency: version 8.0.1 requires @angular/core 8.0.1, while version 8.0.2 necessitates @angular/core 8.0.2. This seemingly small version bump in the core Angular framework signifies potential bug fixes, performance improvements, or subtle API adjustments within the core runtime. Consequently, developers upgrading from @angular/common 8.0.1 to 8.0.2 *must* also upgrade their @angular/core dependency to 8.0.2 to ensure compatibility and avoid unexpected issues.

The release dates also reveal a short interval between versions; 8.0.1 was released on June 13, 2019, and 8.0.2 followed on June 19, 2019 indicating a quick patch or refinement. Therefore, if you're already using Angular 8, upgrading to the @angular/common and @angular/core 8.0.2 pair is generally recommended to benefit from the latest refinements, however, first consult the Angular changelog for detailed information regarding the changes incorporated in @angular/core 8.0.2.

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.