Version Details and Security Vulnerabilities

📦

@angular/common

11.2.0

Comparision Betweeen 11.2.0 and 11.1.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

2865

Unpacked Size

12.23 MB

12.22 MB

Version 11.2.0 Details

Angular Common package versions 11.2.0 and 11.1.2 offer essential directives and services for Angular applications, streamlining common development tasks. While both share the same core functionality and licensing under MIT, understanding the nuances between them is crucial for optimal application stability and performance.

The primary difference lies in their versioning and release dates. Version 11.2.0 was released on February 10, 2021, subsequent to version 11.1.2, which debuted on February 3, 2021. This indicates that 11.2.0 likely includes bug fixes, performance improvements, and potentially minor feature additions on top of the existing 11.1.2 codebase.

Both versions list tslib as a dependency with the same version constraint (^2.0.0), ensuring compatibility with the TypeScript helper library. They also share the same peer dependency on rxjs (^6.5.3), highlighting reliance on the Reactive Extensions library for asynchronous operations and data streams. Crucially, the peer dependency on @angular/core differs, aligning with their respective versions (11.2.0 and 11.1.2), indicating compatibility with the specific Angular core version.

A subtle difference exists in the unpacked size of the distributed package. While both have the same number of files, version 11.2.0 has a slightly larger unpacked size of 12828781 bytes, compared to 12809987 bytes in 11.1.2. This size difference might stem from code optimizations, added features, or updated assets. Developers should generally opt for the latest stable version (11.2.0 at the time of this data) to benefit from the most recent enhancements and bug fixes, assuming compatibility with their existing project setup.

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.