Version Details and Security Vulnerabilities

📦

inquirer

12.9.2

Comparision Betweeen 12.9.2 and 12.9.1

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

70.24 KB

Version 12.9.2 Details

Inquirer.js, a popular Node.js package for building interactive command-line interfaces, has two recently released versions: 12.9.2 and 12.9.1. Both versions maintain the core functionality of providing a collection of user interface elements for CLI interactions. This package simplifies the process of creating interactive prompts for gathering user input directly through the command line. Both versions depend on rxjs, run-async, mute-stream, ansi-escapes, @inquirer/core, and @inquirer/type for streamlined operations and enhancing the user experience.

The key distinction lies in the dependency @inquirer/prompts. Version 12.9.2 uses version 7.8.2 whereas version 12.9.1 uses 7.8.1. This adjustment might involve minor bug fixes, performance tweaks, or new features within the prompt rendering or validation logic. For developers using Inquirer.js, this means potentially improved prompt behavior or enhanced functionality for specific prompt types.

Both versions share identical development dependencies, including 'tshy', '@repo/tsconfig', '@types/mute-stream' and '@arethetypeswrong/cli', assuring a consistent development environment. They also keep the peer dependency @types/node version ">=18", meaning they're developed to be compatible with Node.js versions 18 and above. The package is an MIT licensed package actively maintained by Simon Boudrias.

Given the nature of semantic versioning in npm packages (patch update .1 -> .2), the update from 12.9.1 to 12.9.2 likely contains bug fixes and minor enhancements. Check the specific changelog or release notes for @inquirer/prompts version 7.8.2 to fully understand the exact changes and determine if upgrading is beneficial for your specific use case.

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.