Version Details and Security Vulnerabilities

📦

@angular/router

11.0.7

Comparision Betweeen 11.0.7 and 11.0.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

3 MB

2.99 MB

Version 11.0.7 Details

Angular Router version 11.0.7 introduces subtle yet potentially important refinements over its predecessor, version 11.0.6. Both versions share the same core dependencies, relying on tslib for TypeScript helper functions and maintaining peer dependencies on essential Angular modules like @angular/core, @angular/common, and @angular/platform-browser, ensuring compatibility within the Angular 11 ecosystem. Furthermore, both mandate rxjs version 6.5.3 or higher. The license remains MIT, and the source code resides within the Angular repository on GitHub.

The key differences lie in the updated versions of the peer dependencies in 11.0.7, aligning them with @angular/core, @angular/common, and @angular/platform-browser at version 11.0.7. This update suggests bug fixes, performance improvements, or new features introduced in the broader Angular framework that the router now leverages. Although file count remains identical (85), a slight increase in unpacked size from 3139620 to 3141540 indicates potential code enhancements or added resources. The release date also marks the newest version, being published later.

For developers, this means upgrading to version 11.0.7 of the Angular Router alongside the rest of their Angular 11 dependencies is advisable to benefit from the latest stabilization efforts and potential performance gains within the framework. While no groundbreaking changes appear evident from this data alone, maintaining alignment with the broader Angular ecosystem using 11.0.7 ensures optimal performance and seamless integration. Before upgrading, review the Angular changelog for specific details regarding patches introduced between Angular versions 11.0.6 and 11.0.7, to check for potential breaking changes and impact evaluation..

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.