Version Details and Security Vulnerabilities

📦

@angular/router

6.1.2

Comparision Betweeen 6.1.2 and 6.1.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

158

Unpacked Size

3.94 MB

3.92 MB

Version 6.1.2 Details

Angular Router version 6.1.2 is a minor update to the Angular routing library, building upon the foundation established in version 6.1.1. While the core functionality remains consistent, a key difference lies in the peer dependencies. Version 6.1.2 requires Angular core, common, and platform-browser packages all at version 6.1.2, while the prior version required 6.1.1. This subtle shift often indicates bug fixes or minor feature enhancements within the Angular framework itself that the router leverages. The underlying dependencies like tslib remain compatible with version 1.9.0 or higher, ensuring code compatibility for most existing Angular projects.

Examining the dist object reveals a minor increase in the unpacked size, from 4,109,586 bytes in 6.1.1 to 4,131,230 bytes in 6.1.2. This increase, coupled with the consistent file count, suggests internal optimisations, improved error handling, or slight additions to existing features. Developers upgrading from 6.1.1 should ensure their Angular core dependencies are updated to v6.1.2 to avoid potential conflicts. The release date difference of a few days signifies a relatively quick iteration, commonly implying a focused effort on ironing out recently discovered issues. While the changelog should be consulted for thorough details, developers can generally expect a smooth transition with Angular Router 6.1.2, gaining the benefits of the latest stability improvements and patches in the Angular ecosystem.

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.