Version Details and Security Vulnerabilities

📦

@angular/platform-browser-dynamic

8.1.3

Comparision Betweeen 8.1.3 and 8.1.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

614.12 KB

Version 8.1.3 Details

Angular developers looking to stay current with the framework will find slight but potentially important differences between @angular/platform-browser-dynamic versions 8.1.2 and 8.1.3. Both versions are designed to enable Angular applications to run within a web browser using Just-In-Time (JIT) compilation, a crucial aspect for dynamic rendering and development workflows. They share the same core function: bridging Angular components to the browser's Document Object Model (DOM).

The dependency on tslib remains consistent at ^1.9.0 in both versions, ensuring compatibility with the TypeScript helper library. Similarly, the peer dependencies specify the need for compatible versions of @angular/core, @angular/common, @angular/compiler, and @angular/platform-browser. The key difference lies within the peer dependency versions. Version 8.1.3 requires version 8.1.3 of the packages mentioned before while version 8.1.2 requires version 8.1.2. Therefore, developers upgrading to @angular/platform-browser-dynamic@8.1.3 must also upgrade all their @angular/core, @angular/common, @angular/compiler, and @angular/platform-browser libraries to version 8.1.3 to maintain compatibility and avoid potential conflicts.

Crucially, both versions have the same unpacked size of 628863 bytes and include 69 files within the package. This suggests that the changes introduced in 8.1.3 were likely focused on bug fixes, performance improvements, or minor feature enhancements rather than structural alterations. The time between release dates is around 9 days, implying that there was a good reason for angular team to release 8.1.3 quickly after releasing 8.1.2.

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.