Angular core version 7.1.1 represents a minor update to the core Angular framework, building upon the foundation established by version 7.1.0. Both versions share the same fundamental characteristics: they are described as the core framework for Angular applications, licensed under MIT, and maintained by the Angular team with source code hosted on GitHub. They also share core dependencies, relying on tslib version 1.9.0 or later for TypeScript helpers, and specifying rxjs version 6.0.0 or later and zone.js version 0.8.26 as peer dependencies. This signifies that applications using either version require compatible versions of these libraries to function correctly.
The key difference lies in the update from version 7.1.0 to 7.1.1. Examining the distribution metadata, version 7.1.1 features a slightly smaller file count (605) and a slightly larger unpacked size (19441164 bytes) compared to version 7.1.0 (606 files and 19430121 bytes). Although seemingly a small difference in numbers it can translate in performance improvements. Further, the release date of version 7.1.1 (2018-11-28) is a week later than 7.1.0 (2018-11-21), indicating that 7.1.1 likely includes bug fixes, performance enhancements, or minor feature additions implemented since the previous release.
For Angular developers, this means upgrading from 7.1.0 to 7.1.1 is generally recommended, as it addresses any potential issues present in the earlier version and may offer performance gains. Developers should, as always, consult the official Angular changelog for a detailed breakdown of the specific changes included in version 7.1.1 to understand their impact on existing Angular projects.
All the vulnerabilities related to the version 7.1.1 of the package
Cross site scripting in Angular
A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been classified as problematic. Affected is the handling of comments. The manipulation leads to cross site scripting. It is possible to launch the attack remotely but it might require an authentication first. Upgrading to version 10.2.5, 11.0.5 or 11.1.0-next.3 is advised to to address this issue.