Version Details and Security Vulnerabilities

📦

@angular/router

16.2.10

Comparision Betweeen 16.2.10 and 16.2.9

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

2.18 MB

Version 16.2.10 Details

Angular Router version 16.2.10 represents a minor update over the previous stable release, 16.2.9, within the Angular framework's routing library. Both versions share the same core dependencies, relying on tslib for TypeScript compatibility and aligning with specific versions or ranges of rxjs, @angular/core, @angular/common, and @angular/platform-browser as peer dependencies, ensuring compatibility within the Angular ecosystem. This signifies a consistent architectural foundation between the two releases.

The key difference lies in the version numbers of the peer dependencies. While both versions are compatible with rxjs versions 6.5.3 or ^7.4.0, version 16.2.10 requires @angular/core, @angular/common, and @angular/platform-browser version 16.2.10, while 16.2.9 depends on version 16.2.9 implying the newer version incorporate the latest updates of the core libraries and potentially resolving subtle bugs or incorporating minor enhancements introduced in those core packages. The slight increase in unpacked size from 2283086 to 2283680 in the newer version and the modification of approximately one week between the release dates, respectively October 11th and October 18th, suggests there are some changes. For developers, upgrading to 16.2.10 ensures they are running the most recent iteration of the router library, which benefits the use of the latest Angular versions. If you use the latest Angular libraries, it is important to also upgrade the router.

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.