Angular developers should be aware of a notable update to @angular/platform-browser with the release of version 2.0.1, following closely after version 2.0.0. Both versions serve as the crucial bridge enabling Angular applications to run smoothly within web browsers. This library essentially provides the necessary tools and abstractions for Angular to interact with the Document Object Model (DOM) and manage browser-specific functionalities.
A key difference lies within the declared peer dependencies. Version 2.0.1 exhibits stricter dependency requirements, specifically pinning its compatibility to @angular/core and @angular/common at version "2.0.1" exactly. This is in contrast to version 2.0.0, which employed a more flexible dependency declaration using "^2.0.0", indicating compatibility with any versions starting from 2.0.0 up to but not including 3.0.0.
This subtle change impacts how Angular projects manage dependencies. Upgrading to 2.0.1 requires ensures using angular core and common version 2.0.1, potentially forcing upgrades of related packages. While potentially introducing friction during updates, the locked dependency in 2.0.1 aims to provide more predictable behavior and reduce the risk of unexpected issues arising from minor version mismatches. Developers should consider this carefully when planning Angular application updates to maintain stability. The release date difference of roughly a week also suggests the 2.0.1 may contain bug fixes or minor improvements over 2.0.0.
The are not vulnerabilities for the version 2.0.1 of the package @angular/platform-browser