Version Details and Security Vulnerabilities

📦

@angular/platform-browser

6.0.2

Comparision Betweeen 6.0.2 and 6.0.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

179

Unpacked Size

2.24 MB

Version 6.0.2 Details

Angular developers considering upgrading from version 6.0.1 to 6.0.2 of the @angular/platform-browser package will find a minor, yet potentially impactful, update focused on browser-specific functionalities within the Angular framework. Both versions serve the same core purpose: enabling Angular applications to run seamlessly within web browsers. Key information in the package data reveals subtle differences.

The dependencies remain consistent, with both versions relying on tslib version 1.9.0 or higher. The peer dependencies also align with their respective Angular core and common package versions. Notably, version 6.0.2 depends on @angular/core and @angular/common version 6.0.2, while 6.0.1 requires version 6.0.1 of the same peer dependencies. These direct peer dependencies highlight the importance of maintaining version compatibility across the Angular ecosystem.

The unpacked size of version 6.0.2 is slightly larger, at 2,349,604 bytes compared to 2,349,602 bytes for version 6.0.1, indicating minor code-level changes and/or added assets. Perhaps the most important difference is the release date. Version 6.0.2 was released on May 15, 2018, a few days after version 6.0.1 which was released on May 11, 2018. Given the proximity of release dates, version 6.0.2 likely addresses bug fixes or minor enhancements identified shortly after the 6.0.1 release. Developers should prioritize upgrading to version 6.0.2 to potentially benefit from stability improvements and bug resolutions implemented since the previous release. It's always suggested checking the official Angular changelog for a detailed breakdown of the 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.