Version Details and Security Vulnerabilities

📦

@angular/common

17.3.11

Comparision Betweeen 17.3.11 and 17.3.10

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.88 MB

Version 17.3.11 Details

Angular's @angular/common package provides essential directives and services for building Angular applications. Comparing version 17.3.11 to its immediate predecessor, 17.3.10, reveals subtle but important differences. Both versions share the same core description and licensing under MIT. They also have identical dependencies, relying on tslib version 2.3.0 or higher, and peer dependencies on rxjs (versions 6.5.3 or 7.4.0 and later) and the corresponding @angular/core package. Crucially, @angular/common@17.3.11 depends on @angular/core@17.3.11, while @angular/common@17.3.10 depends on @angular/core@17.3.10.

The most significant difference lies in the version numbers themselves and their release dates. Version 17.3.11 was released on June 5th, 2024, whereas version 17.3.10 was released on May 22nd, 2024. Given the close versioning (17.3.10 vs. 17.3.11), the changes are likely bug fixes, performance improvements, or minor feature additions. For developers, upgrading from 17.3.10 to 17.3.11 is generally recommended to benefit from these improvements and ensure compatibility within an Angular 17.3 environment. The fileCount and unpackedSize remain the same, signaling no major structural alterations, but the updated release date indicates a refinement of the existing codebase. Developers should consult the official Angular changelog and release notes for a detailed breakdown of the specific changes included in the 17.3.11 release.

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.