Version Details and Security Vulnerabilities

📦

@angular/forms

11.2.0

Comparision Betweeen 11.2.0 and 11.1.2

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

Version 11.2.0 Details

Angular Forms version 11.2.0 introduces subtle but important refinements over its predecessor, version 11.1.2. While both versions share the same fundamental architecture for building dynamic and reactive forms in Angular applications, a careful examination reveals key modifications. Both versions depend on tslib v2.0.0 or higher, ensure compatibility with recent TypeScript versions. They also share a liberal MIT license, fostering open-source adoption and modification. The core functionality remains consistent, providing directives and services for creating and managing forms effectively, reflected in identical fileCount and unpackedSize values in their distributions despite the newer release. This suggests that the release mainly focused on improvements without adding new files.

The crucial difference lies in the peer dependencies. The upgrade to version 11.2.0 mandates alignment with Angular Core, Common, and Platform-Browser versions 11.2.0, whereas version 11.1.2 required versions 11.1.2. Essentially, developers upgrading to @angular/forms 11.2.0 must also update their core Angular dependencies to maintain compatibility and leverage any associated bug fixes or performance enhancements introduced in the broader Angular ecosystem. Note that both versions support rxjs ^6.5.3. Developers should prioritize upgrading all related packages together to benefit from the latest bug fixes, security patches, and performance improvements across the entire Angular framework. The release date also indicates a week difference between the 2 versions, released respectively on February 10 and February 3 of 2021.

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.