Version Details and Security Vulnerabilities

📦

gulp-exec

5.0.0

Comparision Betweeen 5.0.0 and 4.0.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

7.3 KB

7.05 KB

Version 5.0.0 Details

Gulp-exec, a plugin designed to execute commands within a Gulp workflow, saw a significant update with the release of version 5.0.0. This version introduces key changes compared to its predecessor, version 4.0.0, that developers should note. Most notably, version 5.0.0 removes the dependency on lodash.template. While seemingly minor, this signifies a shift in how the plugin handles templating or string interpolation, potentially altering the way developers format commands passed to the system shell. In version 4.0.0, lodash.template was utilized for this purpose.

Furthermore, the developer tooling has been bumped. JSHint migrates from 2.9.4 to 2.11.1, while Mocha jumps from version 6.1.4 to 8.0.0. Though these are dev dependencies, it signals a commitment to modern linting and testing practices, indirectly benefiting developers using the plugin by ensuring higher code quality and reliability. Should.js also sees a minor update from 13.2.0 to 13.2.3. The core functionality remains consistent, both versions relying on plugin-error and through2 for error handling and stream processing, respectively. The vinyl dependency stays at ^2.2.0 in both versions.

For developers considering an upgrade, the removal of lodash.template is the primary concern. Existing workflows using lodash.template features might require adjustments to align with the new version. The upgrades of JSHint and Mocha provide reassurance about the package's overall quality. Both versions are licensed under the MIT license.

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.