Version Details and Security Vulnerabilities

📦

tar-stream

1.6.1

Comparision Betweeen 1.6.1 and 1.6.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

26.15 KB

Version 1.6.1 Details

Tar-stream, a lightweight streaming tar parser and generator useful for Node.js environments, saw a minor version update from 1.6.0 to 1.6.1. Both versions maintain the core functionality of parsing and generating tar archives directly in streams, avoiding file system interaction for efficient processing. Developers leveraging tar-stream can extract or create tarballs seamlessly within their applications.

The key difference between the two versions lies in the dependency readable-stream. Version 1.6.0 relies on readable-stream@2.0.0, while version 1.6.1 upgrades this dependency to readable-stream@2.3.0. This upgrade likely includes bug fixes, performance improvements, and potentially new features offered by the newer readable-stream version. For developers, this means potentially improved stability and efficiency when dealing with streams.

Both versions share identical development dependencies, including concat-stream for stream concatenation, standard for code style enforcement, and tape for unit testing, suggesting consistent development practices. They depend on bl, buffer-alloc, end-of-stream, fs-constants, to-buffer and xtend.

The dist object reveals that both versions have the same file count and unpacked size, indicating that the core library structure remained largely unchanged during the update. Version 1.6.1 was released on May 14, 2018, a couple of weeks after version 1.6.0. Potential users should preferably use the latest version 1.6.1 to benefit from bug fixes, and optimizations that might have been introduced in the readable-stream dependency. Ultimately, the upgrade ensures greater reliability and compatibility.

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.