Version Details and Security Vulnerabilities

📦

@angular/common

13.3.7

Comparision Betweeen 13.3.7 and 13.3.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

2961

Unpacked Size

10.86 MB

Version 13.3.7 Details

Angular's @angular/common package provides essential directives, pipes, and services for building Angular applications. Analyzing versions 13.3.7 and 13.3.6 reveals subtle but potentially impactful changes for developers. Both versions share a common foundation, including dependencies like tslib and peer dependencies on rxjs and @angular/core. They also maintain identical fileCount and unpackedSize values within their distribution packages. Examining peerDependencies show us that both versions are compatible with rxjs version from 6.5.3 to 7.4.0.

The key difference lies in the @angular/core peer dependency version requirement. While 13.3.6 requires @angular/core@13.3.6, version 13.3.7 necessitates @angular/core@13.3.7. Therefore developers must upgrade also the @angular/core package if they want to upgrade @angular/common.

Another key difference is the release date: version 13.3.7 was released on May 11, 2022, a week later the version 13.3.6 released on May 4, 2022. Upgrading from 13.3.6 to 13.3.7 likely involves minor bug fixes and refinements aligned with the corresponding @angular/core release. Developers should consult the official Angular changelog and release notes to understand the specific changes introduced in 13.3.7 and assess their impact on existing applications. Keeping both @angular/common and @angular/core synchronized ensures optimal compatibility and access to the latest features and improvements within the Angular ecosystem.

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.