Version Details and Security Vulnerabilities

📦

@yarnpkg/fslib

2.2.0

Comparision Betweeen 2.2.0 and 2.1.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

203.06 KB

165.57 KB

Version 2.2.0 Details

@yarnpkg/fslib is a file system library designed for robust and consistent file operations within the Yarn ecosystem. Version 2.2.0 introduces enhancements over the previous stable version, 2.1.0, offering developers improvements in file handling and archive management capabilities. A key difference lies in the updated dependency on @yarnpkg/libzip, moving from version 2.1.0 to 2.2.0, suggesting potential updates and bug fixes within the underlying ZIP archive handling logic.

The update also shows a significant increase in both the file count (from 33 to 41) and the unpacked size (from 169,541 bytes to 207,929 bytes). This suggests the addition of new features, expanded functionality, or more comprehensive test coverage in the newer version, potentially offering a wider range of file system utilities. Developers should carefully investigate these new additions, as they could unlock more efficient file manipulations within their Yarn-based projects.

The release date of 2.2.0 is August 28, 2020, a little over a month after version 2.1.0 was released, indicating a relatively rapid iteration cycle and possibly addressing critical issues or adding highly requested features. When upgrading, developers should review the changelog for detailed information on breaking changes. The library, licensed under BSD-2-Clause, remains under the Yarnpkg/berry repository on GitHub and provides a dependable means of handling file system interactions.

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.