Version Details and Security Vulnerabilities

📦

yargs

3.18.0

Comparision Betweeen 3.18.0 and 3.17.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 3.18.0 Details

Yargs versions 3.18.0 and 3.17.1 offer lightweight option parsing, transforming command-line arguments into a readily usable JavaScript object. Both versions share similar core functionality, providing developers with tools for defining and interpreting command-line options. Notably, the dependency tree remains consistent across both versions, relying on packages like y18n for internationalization, cliui for building command-line user interfaces, camelcase and decamelize for string transformations, and window-size for terminal window detection. Development dependencies, used for testing and code quality, also remain identical between versions, including nyc for code coverage, chai for assertions, mocha for testing framework, hashish for utility functions, standard for code style enforcement, and coveralls for coverage reporting.

The primary distinction lies in the release date of 3.18.0, which is August 6, 2015, compared to 3.17.1's release on August 2, 2015. This suggests that version 3.18.0 incorporates bug fixes, minor enhancements, or internal refactoring implemented within that brief period. While the functional API appears unchanged based on the provided data, developers should consult the full changelog for detailed insight on the nature of these updates. The library is licensed under MIT, encouraging open use and modification. Both versions are from the same repository, ensuring developers can access the source code and contribute to the project. These versions, authored by Alex Ford, provide a stable and reliable foundation for handling command-line arguments in Node.js applications and the core functionality is maintained in both versions enabling developers to use the most suitable for them.

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.