Version Details and Security Vulnerabilities

📦

@angular/platform-browser-dynamic

4.4.1

Comparision Betweeen 4.4.1 and 4.3.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 4.4.1 Details

Angular developers considering updating their applications should note the subtle yet crucial differences between @angular/platform-browser-dynamic versions 4.3.6 and 4.4.1. Both versions serve the purpose of enabling Angular applications to run within a web browser environment utilizing Just-In-Time (JIT) compilation. The newer version, 4.4.1, released on September 15, 2017, builds upon its predecessor, 4.3.6 (released August 23, 2017), while maintaining the MIT license and the same Git repository.

The most significant change resides in the peer dependencies. Version 4.4.1 requires core Angular packages (@angular/core, @angular/common, @angular/compiler, and @angular/platform-browser) to also be at version 4.4.1. Conversely, version 4.3.6 necessitates these dependencies to be at version 4.3.6. This strict requirement for perfectly matching peer dependencies is vital for stability and to avoid potential conflicts or unexpected behavior within an Angular application. While both depend on tslib version '^1.7.1', the core libraries must stay aligned.

Therefore, when upgrading to @angular/platform-browser-dynamic@4.4.1, developers must concurrently update all other @angular/* packages within their project to version 4.4.1 to ensure compatibility and avoid runtime errors. The update likely includes bug fixes and performance improvements. Check the official angular changelog for more info about the changes included on new versions.

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.