Version Details and Security Vulnerabilities

📦

inquirer

12.2.0

Comparision Betweeen 12.2.0 and 12.1.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

70.05 KB

Version 12.2.0 Details

Inquirer.js version 12.2.0 introduces subtle yet noteworthy updates compared to its predecessor, version 12.1.0, primarily focusing on dependency enhancements within the interactive command-line interface toolkit. Developers upgrading to 12.2.0 will primarily notice changes in the internal dependencies, specifically the @inquirer/core and @inquirer/prompts packages. @inquirer/core sees an update from version 10.1.0 to 10.1.1, and @inquirer/prompts jumps from 7.1.0 to 7.2.0.

While the core functionality of Inquirer.js remains consistent, these updated dependencies likely incorporate bug fixes, performance improvements, or minor feature additions within those specific modules. This suggests improvements in the underlying plumbing that supports the prompting and user interface elements. Developers should benefit from these updates through potentially more stable and refined interactions. The other dependencies such as rxjs, run-async, mute-stream, ansi-escapes and the devDependencies are kept at the same version.

The unchanged number of files (17) and unpacked size (71735 bytes) between the two versions indicate that the main package structure remains similar, meaning upgradation should be relatively seamless without major code refactoring on the developer side. The release date difference indicates a relatively short time between the two versions, suggesting that version 12.2.0 is possibly fixing some small issues found on 12.1.0. For developers already using Inquirer.js, upgrading to 12.2.0 provides access to the latest refinements and ensures compatibility with the newest features and bug fixes within the @inquirer/core and @inquirer/prompts dependencies, ultimately contributing to a more robust and user-friendly command-line experience.

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.