Version Details and Security Vulnerabilities

📦

@yarnpkg/fslib

3.1.0

Comparision Betweeen 3.1.0 and 3.0.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

226.08 KB

225.39 KB

Version 3.1.0 Details

Version 3.1.0 of @yarnpkg/fslib introduces subtle but potentially impactful changes compared to its predecessor, version 3.0.2. Both versions maintain tslib as a core dependency, ensuring compatibility and consistent Typescript helper functionality. However, the key divergence lies in the development dependencies. Version 3.1.0 utilizes @yarnpkg/libzip version ^3.1.0, whereas version 3.0.2 depended on @yarnpkg/libzip version ^3.0.1.

This update to @yarnpkg/libzip likely includes bug fixes, performance improvements, or new features within the libzip integration itself, potentially impacting how @yarnpkg/fslib handles zip archive interactions. Developers utilizing features involving zip files should carefully review the changelog for @yarnpkg/libzip to understand the specific changes introduced in the newer version.

The difference in unpacked size, with version 3.1.0 being slightly larger (231501 bytes) than version 3.0.2 (230799 bytes), suggests that new features or modifications have been incorporated into the newer release, further emphasizing the importance of examining the release notes. Finally, the release date difference of almost 4 months (May 8, 2024 vs January 30, 2024) indicates the accumulation of several changes that could affect developers using file system utilities. By keeping abreast of these updates, developers can ensure they capitalize on the latest enhancements and address any potential compatibility risks.

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.