Version Details and Security Vulnerabilities

📦

@angular/router

10.2.0

Comparision Betweeen 10.2.0 and 10.1.6

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

Version 10.2.0 Details

Version 10.2.0 of the Angular Router presents a subtle but significant update compared to version 10.1.6, primarily focusing on compatibility and potential bug fixes. Both versions share the same core dependencies like tslib and the same number of files (84) with identical unpacked size, indicating no major feature additions or substantial code refactoring impacting the library's footprint. The dependency requirements remain consistent, allowing for a smooth transition between the two.

The core difference lies in the peer dependencies. Version 10.2.0 requires @angular/core, @angular/common, and @angular/platform-browser at version 10.2.0, aligning the router with the broader Angular framework's version. Previously, version 10.1.6 required 10.1.6 of the same peer dependencies. This ensures developers are utilizing the correct router version for their Angular application's core version, preventing potential compatibility issues, unforeseen bugs, and ensuring optimal performance. Developers will experience an improved, properly aligned routing mechanism when upgrading to 10.2.0 with the corresponding matching Angular packages. The release date difference of approximately one week also suggests a focused effort on quickly delivering targeted fixes or compatibility improvements to the Angular ecosystem. If you have an Angular application using version 10.2.0, is recommended to keep the versions consistent using the @angular/router version 10.2.0.

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.