Version Details and Security Vulnerabilities

📦

ternary-stream

1.2.2

Comparision Betweeen 1.2.2 and 1.2.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 1.2.2 Details

Ternary-stream is a lightweight npm package designed to conditionally fork a stream based on a provided condition, effectively creating a branching data flow. It also offers capabilities to collect data from downstream streams, simplifying complex data processing pipelines. The package leverages other stream-related utilities like duplexer2, merge-stream, fork-stream, and through2 to achieve its functionality, offering a composable approach to stream manipulation.

Version 1.2.2 improves upon the previous 1.2.1, showcasing subtle yet notable updates in its dependency requirements. Specifically, merge-stream is updated from ~0.1.5 to ~0.1.6, and through2 moves from ~0.6.1 to ~0.6.3. These dependency upgrades often bring bug fixes and performance improvements. On the developer tooling side, jshint is bumped from ^2.5.5 to ^2.5.6, mocha moves from ^1.21.4 to ^2.0.0, and should shifts from ^4.0.4 to ^4.1.0. Upgrading Mocha specifically usually brings significant testing framework enhancements.

For developers considering using ternary-stream, these changes suggest a push towards stability and leveraging the latest features from upstream libraries. When adopting version 1.2.2, developers may want to review the changelogs of the upgraded dependencies to understand the precise nature of the improvements and ensure compatibility with their existing projects. While the core functionality remains consistent, these dependency updates could positively impact overall performance, reliability, and the developer experience.

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.