Version Details and Security Vulnerabilities

📦

@angular/common

13.2.3

Comparision Betweeen 13.2.3 and 13.2.2

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

Angular's @angular/common package, a crucial component for building robust Angular applications, saw a minor version update from 13.2.2 to 13.2.3. Both versions share the same fundamental purpose: providing commonly needed directives and services. They also maintain identical dependencies on tslib (version ^2.3.0), ensuring compatibility with TypeScript helper functions. The peer dependencies, rxjs (version ^6.5.3 || ^7.4.0) and @angular/core are also updated to the corresponding version, highlighting the tight integration of common utilities with the core framework and reactive extensions.

While seemingly a small increment, the update introduces subtle but potentially significant refinements. The unpacked size of version 13.2.3 increased slightly to 11,384,436 bytes from 11,383,489 bytes, a difference of nearly 1KB implying addition or modification of features, bug fixes, or performance improvements. Developers considering the update should investigate the changelog for specific details regarding bug fixes, performance enhancements, or new features introduced in 13.2.3. The newer has a release date which is about 9 days later, meaning, it contains new features accumulated in that time interval.

For developers using Angular, staying up-to-date with the latest minor versions is generally recommended to benefit from bug fixes, performance improvements, and new features. However, it's crucial to review the changelog and potentially run tests to ensure compatibility with existing code, especially when there are changes to package size. The specific changes can improve the performance and the stability of your projects. This guarantees a smooth transition and avoids potential breakage in your application after updating.

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.