Version Details and Security Vulnerabilities

📦

@angular/router

4.3.5

Comparision Betweeen 4.3.5 and 4.3.4

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 4.3.5 Details

Angular developers seeking a routing solution for their applications can leverage the @angular/router package, a crucial part of the Angular framework. Comparing versions 4.3.5 and 4.3.4 reveals subtle but potentially important distinctions. Both versions share the same core description as "Angular - the routing library" and maintain consistent licensing under MIT. They also depend on tslib version ^1.7.1 for TypeScript helper functions. The key difference lies in their peer dependencies and release dates. Version 4.3.5 requires @angular/core, @angular/common, and @angular/platform-browser all at exactly version 4.3.5, while 4.3.4 necessitates version 4.3.4 for those same peer dependencies. Both versions require rxjs version ^5.0.1. This indicates that version 4.3.5 includes updates and fixes specifically targeting the corresponding Angular core components. Developers upgrading from 4.3.4 should ensure that they also update their @angular/core, @angular/common, and @angular/platform-browser packages to 4.3.5 to guarantee compatibility. The release dates further highlight this divergence, with 4.3.5 being released on August 16, 2017, a week after version 4.3.4, released on August 10, 2017. Thus, the newer version likely addresses bugs or incorporates minor improvements discovered in the earlier release, highlighting the importance of staying current with Angular's ecosystem for optimal performance and stability in routing functionalities such as navigation, route parameters and lazy loading modules.

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.