Version Details and Security Vulnerabilities

📦

@angular/platform-browser

13.0.1

Comparision Betweeen 13.0.1 and 13.0.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

1.01 MB

Version 13.0.1 Details

Angular developers considering the @angular/platform-browser package should be aware of the subtle but important differences between versions 13.0.0 and 13.0.1. Both versions serve as the crucial bridge between the Angular framework and the web browser environment, enabling Angular applications to run within a browser. They share the same core dependencies, relying on tslib version 2.3.0 or higher for TypeScript helper functions. Crucially, they also share peer dependencies on @angular/core, @angular/common, and @angular/animations, indicating they are designed to work seamlessly with corresponding versions of these core Angular modules.

The key difference lies in the specific versions of these peer dependencies. Version 13.0.0 requires versions 13.0.0 of @angular/core, @angular/common, and @angular/animations, while version 13.0.1 bumps these requirements to 13.0.1. What this means in practice is that version 13.0.1 likely incorporates bug fixes and minor improvements that necessitate alignment with the 13.0.1 versions of the core Angular packages. Developers upgrading from 13.0.0 *must* also update their @angular/core, @angular/common, and @angular/animations packages to 13.0.1 to ensure compatibility and avoid potential runtime errors. Looking at the dist data, version 13.0.1 is slightly larger (1057794 unpackedSize) compared to 13.0.0 (1057552 unpackedSize). The difference in release dates (2021-11-10 for 13.0.1 vs 2021-11-03 for 13.0.0) confirms that 13.0.1 is a patch release addressing issues found shortly after the initial 13.0.0 release. Therefore, upgrading to 13.0.1 alongside its peer dependencies is generally recommended for the most stable and up-to-date experience.

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.