Version Details and Security Vulnerabilities

📦

@types/jasmine

4.0.2

Comparision Betweeen 4.0.2 and 4.0.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

55.38 KB

Version 4.0.2 Details

The @types/jasmine package provides TypeScript definitions for the Jasmine testing framework, enabling developers to write type-safe Jasmine tests in their TypeScript projects. Comparing versions 4.0.2 and 4.0.1, while seemingly minor, reveals subtle improvements. Both packages maintain the same core structure, licensing under MIT, and originating from the DefinitelyTyped repository. The package.json structure remains mostly identical, indicating a high degree of stability and backwards compatibility.

A key difference lies in the releaseDate. Version 4.0.2 was released on March 31, 2022, while version 4.0.1 came out on March 29, 2022. This suggests that 4.0.2 incorporates fixes or minor enhancements developed in the intervening days. Another minor difference is in unpackedSize. Version 4.0.2 has unpackedSize as 56704 and 4.0.1 has 56705 indicating that version 4.0.2 probably has slightly changed files. Developers upgrading from 4.0.1 to 4.0.2 should expect a seamless transition with potential bug fixes or minor improvements. For new users, starting with 4.0.2 ensures they benefit from the latest refinements. The fileCount is the same in the two versions. Because the versions have the same fileCount, it means that the changes in the newer version did not add or remove any files. Developers should review the commit history on the DefinitelyTyped repository for detailed change logs describing the specific fixes or enhancements included in the newer version. Because both versions share the same dependencies, the changes are probably related to the structure of the existing types or their implementations.

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.