Version Details and Security Vulnerabilities

📦

module-deps

4.0.0

Comparision Betweeen 4.0.0 and 3.9.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 4.0.0 Details

Module-deps, a library for traversing JavaScript dependency graphs and generating JSON output suitable for browser-pack, saw a significant update from version 3.9.1 to 4.0.0. Both versions maintain the core functionality of walking dependencies, but the upgrade introduces changes in underlying stream handling.

One key difference lies in the readable-stream dependency. Version 3.9.1 relies on readable-stream version 1.1.13, while version 4.0.0 upgrades this to version 2.0.2. This is a noteworthy change as readable-stream v2 represents a significant shift in the Node.js Streams API, aligning more closely with the standard and offering potentially improved performance and error handling. Developers should be aware of this upgrade in stream implementation when migrating. Moreover, through2 dependency has been updated from version 1.0.0 to 2.0.0.

Another important difference is the concat-stream dependency, updated from ~1.4.5 to ~1.5.0. This upgrade brings improvements and possible bug fixes.

Apart from these, the dependencies on JSONStream, browser-resolve, defined, detective, duplexer2, inherits, parents, resolve, stream-combiner2, subarg, xtend, tap and browser-pack remain consistent between the two. As a result, upgrading to module-deps 4.0.0 offers up-to-date stream features with its upgraded dependency on readable-stream, potentially leading to performance improvements and better alignment with modern stream standards which would be a compelling reason to upgrade.

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.