Angular developers looking to leverage the @angular/platform-browser package should note the subtle, but potentially impactful, differences between versions 2.1.0 and 2.0.2. The newer version, 2.1.0, released on October 12, 2016, builds upon the foundation laid by its predecessor, 2.0.2 which saw daylight on October 6, 2016. While both versions share the same core description—an Angular library facilitating web browser integration— they are distinguished by their peer dependencies.
Crucially, version 2.1.0 necessitates @angular/core and @angular/common at version "2.1.0" as well. This update suggests that version 2.1.0 likely incorporates bug fixes, performance improvements, or new features that rely on updated functionalities within the core Angular framework and common modules. Developers upgrading to @angular/platform-browser@2.1.0 must ensure that @angular/core and @angular/common are also updated to the corresponding "2.1.0" versions to maintain compatibility and avoid potential runtime errors. The six-day gap between releases could indicate responses and improvements derived from real-world usage and initial feedback related to version 2.0.2. As always, reviewing the official Angular changelog for specific details regarding fixes and feature additions introduced in version 2.1.0 is highly advised before upgrading.
The are not vulnerabilities for the version 2.1.0 of the package @angular/platform-browser