Angular developers should be aware of a subtle but potentially important update in @angular/common version 2.1.1 compared to the previous stable version, 2.1.0. Both versions provide essential directives and services crucial for building Angular applications, including tools for internationalization, location, and common data transformations. They both share the same MIT license and are maintained by the Angular team. The core functionality remains consistent, focusing on building dynamic user interfaces and handling common web development tasks.
The key difference lies in the peer dependency: version 2.1.1 requires @angular/core version 2.1.1, while version 2.1.0 depends on @angular/core version 2.1.0. This suggests that version 2.1.1 might include bug fixes or minor adjustments specifically tailored to work optimally with the corresponding @angular/core release. Developers should ensure their @angular/core package is also updated to 2.1.1 when upgrading @angular/common to avoid potential compatibility issues. While the descriptions are identical, indicating no major feature additions, keeping both @angular/common and @angular/core in sync is generally a best practice for Angular development. The release dates suggest a relatively short timeframe between the two versions, hinting that 2.1.1 was likely a patch release addressing specific issues identified in 2.1.0. Ensure that your Angular CLI takes advantage of this update to guarantee stability.
The are not vulnerabilities for the version 2.1.1 of the package @angular/common