Version Details and Security Vulnerabilities

📦

@angular/common

14.2.1

Comparision Betweeen 14.2.1 and 14.2.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

3008

Unpacked Size

11.55 MB

Version 14.2.1 Details

Angular’s @angular/common package provides essential directives and services for building Angular applications. Comparing version 14.2.1 with its predecessor, 14.2.0, we see a minor version bump indicating mostly bug fixes and smaller improvements rather than major feature additions. While both versions share the same core description and license (MIT), the key differences lie in their release dates and potentially the internal code. Version 14.2.1 was released on September 7, 2022, while 14.2.0 came out on August 25, 2022.

Developers should note that both versions list rxjs (versions 6.5.3 or 7.4.0 and later) and @angular/core as peer dependencies. This means your project needs to have these packages installed separately and at compatible versions. For version 14.2.1 that means having @angular/core at version 14.2.1, while 14.2.0 requires @angular/core at version 14.2.0. The tslib dependency remains consistent across both versions, requiring version 2.3.0 or higher. The slight difference in unpacked size on disk, 12115232 bytes for 14.2.1 versus 12115906 bytes for 14.2.0 hints at optimized code or potentially removed files in the newer version. Also note that both packages have 3008 files in each of them.

For developers, upgrading from 14.2.0 to 14.2.1 offers the stability and reliability of the latest patch, with bug fixes and minor enhancements. Always check the Angular changelog for detailed lists of changes between versions to fully understand any impact on your application.

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.