Version Details and Security Vulnerabilities

📦

type-fest

2.3.2

Comparision Betweeen 2.3.2 and 2.3.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

143.83 KB

143.21 KB

Version 2.3.2 Details

Type-Fest is a popular npm package offering a curated collection of essential TypeScript types, designed to enhance developer productivity and type safety in TypeScript projects. Comparing versions 2.3.2 and 2.3.1 reveals subtle but important differences. Both share the same core development dependencies, including xo for linting, tsd for type definition testing, typescript itself, expect-type for assertion testing, and @sindresorhus/tsconfig for consistent TypeScript configuration. This consistency ensures continuity in the development environment. Both versions also maintain the same licensing, repository, author, and funding information, signaling a stable and well-maintained project.

The key differences lie in the dist object and the releaseDate. Version 2.3.2 was released on September 10, 2021, at 14:40:36.112Z, while version 2.3.1 came out earlier the same day at 04:27:26.397Z. Most notably the fileCount and unpackedSize fields within the dist object are incremented. Version 2.3.2 contains 64 files with an unpacked size of 147286 bytes, compared to version 2.3.1's 63 files and 146651 bytes. This increment suggests that version 2.3.2 includes minor additions, bug fixes, or enhancements to existing type definitions.

For developers, these differences highlight the ongoing evolution and refinement of the Type-Fest library. While the core functionality remains consistent, the incremental changes in file count and unpacked size point to continued efforts to improve the quality and comprehensiveness of the type definitions offered. Therefore, upgrading to version 2.3.2 ensures users have access to the latest improvements and potential bug fixes within the type-fest collection.

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.