Version Details and Security Vulnerabilities

📦

@angular/common

6.0.9

Comparision Betweeen 6.0.9 and 6.0.8

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

2364

Unpacked Size

11.76 MB

Version 6.0.9 Details

Angular developers should be aware of the subtle yet potentially impactful differences between @angular/common versions 6.0.9 and 6.0.8. Both versions, described as providing commonly needed directives and services for Angular applications, share core characteristics. They both depend on tslib version 1.9.0 or higher and list rxjs version 6.0.0 or higher, along with the corresponding @angular/core version(6.0.8 and 6.0.9), as peer dependencies. This indicates a shared foundation and compatibility with the broader Angular ecosystem of that time. Both versions are licensed under the MIT license and are maintained by the Angular team, residing in the same GitHub repository.

However, a key distinction lies in the @angular/core peer dependency: version 6.0.9 requires @angular/core version 6.0.9, while version 6.0.8 naturally depends on @angular/core 6.0.8. The releaseDate also differs, with version 6.0.9 being released shortly after 6.0.8. While the fileCount remains the same at 2364, The unpacked size is slightly different, developers upgrading should understand if that can be affecting their final bundle sizes. This quick release cycle suggests that version 6.0.9 likely addresses specific bug fixes or minor improvements introduced in or exposed by version 6.0.8. Developers should upgrade to the latest 6.0.9 to ensure access to the most current bug fixes and improvements in the 6.x series. Although information regarding the bug fixes are not present in the data, Angular usually provides a changelog.

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.