Version Details and Security Vulnerabilities

📦

@angular/platform-browser-dynamic

7.2.0

Comparision Betweeen 7.2.0 and 7.1.4

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

615.27 KB

614.05 KB

Version 7.2.0 Details

Angular's @angular/platform-browser-dynamic package facilitates running Angular applications in web browsers using Just-In-Time (JIT) compilation. Comparing version 7.2.0 with the previous stable version, 7.1.4, presents subtle but potentially impactful differences. Both versions share identical descriptions and dependencies, relying on tslib for TypeScript helper functions and listing @angular/core, @angular/common, @angular/compiler, and @angular/platform-browser as peer dependencies, ensuring compatibility within the Angular ecosystem. The core functionality remains consistent: enabling dynamic Angular applications within a browser environment.

Key differentiators lie in the version numbers of peer dependencies. Version 7.2.0 expects peer dependencies of the same version (7.2.0), whereas 7.1.4 expects 7.1.4 versions. Developers should ensure that the versions of @angular/core, @angular/common, @angular/compiler, and @angular/platform-browser align with the @angular/platform-browser-dynamic version to avoid compatibility issues. Furthermore, the dist object reveals slightly different unpackedSize values – 630039 bytes for 7.2.0 compared to 628792 bytes for 7.1.4, suggesting minor code changes or optimizations. The release dates also highlight the gap between versions, with 7.2.0 released on January 7, 2019, and 7.1.4 released on December 18, 2018. Therefore, upgrading from 7.1.4 to 7.2.0 involves updating peer dependencies and acknowledging possible, although minor, changes in the compiled code. Developers should consult the Angular changelog for detailed release notes outlining specific fixes, features, or performance enhancements introduced in version 7.2.0.

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.