Version Details and Security Vulnerabilities

📦

@angular/common

18.2.10

Comparision Betweeen 18.2.10 and 18.2.9

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

3016

Unpacked Size

10.94 MB

Version 18.2.10 Details

Angular developers should be aware of the recent updates to @angular/common, specifically the jump from version 18.2.9 to 18.2.10. Both versions, as their descriptions state, provide commonly needed directives and services for Angular applications. A key takeaway is that the core dependencies remain consistent. Both versions depend on tslib at ^2.3.0 ensuring compatibility for TypeScript helpers across your projects. The peer dependencies also remain the same, requiring rxjs at either version ^6.5.3 || ^7.4.0 and @angular/core at their respective version. This indicates no breaking API changes pertaining to these fundamental dependencies occurred between the releases.

However, a noteworthy difference lies in the dist object. While both versions contain the same number of files (3016), the unpacked size differs slightly: 11475183 bytes for 18.2.9 and 11475549 bytes for 18.2.10. This suggests that some of the files have been modified or added which contributes to the size increase. The release dates also highlight the recency of these releases (October 23rd and October 30th of 2024 respectevely). The changes between the versions may contain bug fixes, performance improvements, or minor feature enhancements, even if the dependencies haven't changed. For most developers, upgrading from 18.2.9 would generally be recommended to benefit from the latest enhancements and bug fixes. For detailed insights, it is always advisable to consult the official Angular changelog or release notes on the Angular GitHub repository.

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.