Version Details and Security Vulnerabilities

📦

grunt-contrib-nodeunit

0.3.0

Comparision Betweeen 0.3.0 and 0.2.2

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 0.3.0 Details

Grunt-contrib-nodeunit, a Grunt plugin designed to execute Nodeunit unit tests, sees a notable update moving from version 0.2.2 to 0.3.0. Both versions share the core functionality of running unit tests with Nodeunit and depend on the same core Nodeunit library version, "nodeunit": "~0.8.0". However, the newer 0.3.0 version introduces improvements and changes in its development dependencies.

Specifically, version 0.3.0 has upgraded its development dependencies with "grunt-contrib-jshint":"~0.8.0", "grunt-contrib-internal":"~0.4.6", and includes two new development dependencies: "grunt-contrib-clean":"~0.5.0" and "tap":"~0.4.6". Comparing this to version 0.2.2, which uses older versions like "grunt-contrib-jshint":"~0.5.4" and "grunt-contrib-internal":"~0.4.5" and lacks the clean and tap dependencies, suggests a focus on enhanced code quality, internal tooling, and potentially more robust testing processes in the newer release. The inclusion of grunt-contrib-clean indicates the addition of tasks for cleaning up files and directories, while tap suggests integration with the Test Anything Protocol for standardized test result output. This will help you have a more performant library and increased test coverage.

Developers upgrading to version 0.3.0 can expect improvements in the underlying tooling, potentially leading to a smoother development workflow. The peer dependency on "grunt": "~0.4.0" remains consistent across both versions, ensuring compatibility with Grunt 0.4.x. The newer version was released on January 27, 2014, a few months after the release of 0.2.2 on October 19, 2013.

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.