Version Details and Security Vulnerabilities

📦

@angular/platform-browser

2.2.0

Comparision Betweeen 2.2.0 and 2.1.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 2.2.0 Details

Angular developers looking to leverage the @angular/platform-browser package should be aware of key differences between versions 2.2.0 and 2.1.2. Both versions serve as the entry point for running Angular applications within web browsers, providing essential services and tools to interact with the DOM and manage browser-specific functionalities. However, the update from 2.1.2 to 2.2.0 includes crucial improvements worth noting.

Primarily, the peer dependencies are updated. Version 2.2.0 requires @angular/core and @angular/common at version 2.2.0, while 2.1.2 depends on the 2.1.2 versions of these core packages. This dependency shift signifies underlying changes and potentially bug fixes or performance enhancements within the Angular framework itself. Developers must ensure that their core Angular packages are updated to version 2.2.0 when upgrading @angular/platform-browser to 2.2.0 to maintain compatibility and prevent potential runtime errors.

Furthermore, the release date difference indicates a relatively short period between releases, approximately two and a half weeks. This suggests that version 2.2.0 likely contains incremental improvements and bug fixes rather than a significant architectural overhaul. While the descriptions remain the same, focusing on their role as the browser-specific Angular library, developers should consult the official Angular changelog or release notes for a comprehensive overview of the specific changes, bug fixes, and potential breaking changes introduced in version 2.2.0. Always prioritize thorough testing after upgrading to any new version to ensure application stability.

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.