Version Details and Security Vulnerabilities

📦

cucumber

1.2.0

Comparision Betweeen 1.2.0 and 1.1.0

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.0 Details

Cucumber version 1.2.0 represents an incremental update over its predecessor, version 1.1.0, in this popular JavaScript implementation of the Cucumber testing framework. Both versions share a core set of dependencies vital for behavior-driven development (BDD), including 'co' for generator-based control flow, 'glob' for file system path matching, 'colors' for enhanced console output, 'lodash' for utility functions, 'gherkin' for parsing Gherkin feature files, and other essential modules like 'callsite', 'duration', 'cli-table', 'commander', 'camel-case', 'stack-chain' and 'is-generator'. Cucumber-html is also present in both versions which enables HTML reporting.

A key difference lies in the removal of the 'base-64' dependency in version 1.2.0, indicating a shift in how the package handles base64 encoding, potentially through alternative methods or integration with other libraries. This change could affect existing users who relied on the 'base-64' module directly, requiring them to adapt their code accordingly.

Both versions rely on an identical suite of development dependencies, encompassing tools for testing, linting, and building, such as 'tmp', 'pogo', 'async', 'sinon', 'jshint', 'rimraf', 'ansi_up', 'connect', 'jasmine', 'exorcist', 'fs-extra', 'json-diff', 'browserify', 'serve-static', and 'coffee-script'. This consistency ensures a similar development workflow across both versions.

The release dates show version 1.2.0 was released shortly after 1.1.0.

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.