Version Details and Security Vulnerabilities

📦

@angular/platform-browser-dynamic

10.1.2

Comparision Betweeen 10.1.2 and 10.1.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

476.79 KB

Version 10.1.2 Details

Angular developers relying on Just-In-Time (JIT) compilation in the browser will find the @angular/platform-browser-dynamic package essential. Comparing versions 10.1.1 and 10.1.2 reveals subtle but important updates. Both versions depend on "tslib" version ^2.0.0, ensuring compatibility with recent TypeScript features. They share the same file count (44) and unpacked size (488231 bytes), suggesting that the code changes were primarily focused on internal logic or bug fixes rather than adding significant new features affecting the overall size.

Crucially, both rely on peer dependencies of other core Angular modules: @angular/core, @angular/common, @angular/compiler, and @angular/platform-browser. A key difference lies in the versions of these peer dependencies. Version 10.1.2 expects versions 10.1.2 of these packages, while 10.1.1 naturally depends on 10.1.1 versions. This means upgrading to @angular/platform-browser-dynamic@10.1.2 necessitates upgrading the entire core Angular framework to maintain compatibility.

The release dates highlight the timelines: 10.1.1 was released on September 9th, 2020, and 10.1.2 on September 16th, 2020, just a week apart. This suggests that 10.1.2 likely addresses bug fixes or minor enhancements identified shortly after the 10.1.1 release. Developers should prioritize using version 10.1.2 for the latest fixes, ensuring they update all core Angular dependencies simultaneously to avoid potential conflicts or unexpected behavior.

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.