Version Details and Security Vulnerabilities

📦

@angular/common

4.3.2

Comparision Betweeen 4.3.2 and 4.3.1

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.3.2 Details

Angular developers considering an update to @angular/common should note the transition from version 4.3.1 to 4.3.2. This incremental update, released on July 27, 2017, builds upon the foundation of the previous stable version, 4.3.1, released just over a week prior on July 19, 2017. Both versions share identical descriptions, outlining @angular/common as a provider of commonly needed directives and services within the Angular framework. Key dependencies, such as tslib with a version requirement of "^1.7.1", remain consistent, ensuring compatibility with TypeScript helper functions.

The pivotal difference lies in the peerDependencies. Version 4.3.2 is tied to @angular/core version 4.3.2, whereas version 4.3.1 requires @angular/core version 4.3.1. This indicates that upgrading to @angular/common@4.3.2 necessitates a corresponding upgrade to @angular/core@4.3.2. Developers should carefully manage their Angular core version to avoid potential compatibility issues. Developers should examine the Angular changelog for the specific changes introduced in @angular/core@4.3.2 to understand the full impact of this upgrade. Given the short time span between releases, the changes are likely patch fixes and minor improvements for the core functionalities. As with all angular updates, always check the official github repository for the full changelog list.

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.