Version Details and Security Vulnerabilities

📦

inquirer

12.4.1

Comparision Betweeen 12.4.1 and 12.4.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

71.03 KB

71.34 KB

Version 12.4.1 Details

Inquirer.js, a popular npm package providing interactive command-line user interfaces, released version 12.4.1 as a minor update to the preceding stable version 12.4.0. Both versions retain the core functionality of the library, offering a collection of tools for creating engaging and user-friendly CLI experiences. Key dependencies like rxjs, run-async, mute-stream, and ansi-escapes remain consistent between the two versions, ensuring a stable foundation for developers.

The primary differences lie in the updated versions of its internal @inquirer scoped packages. Specifically, @inquirer/core has been bumped from 10.1.5 to 10.1.6, @inquirer/type from 3.0.3 to 3.0.4, and @inquirer/prompts from 7.3.0 to 7.3.1. These updates likely contain bug fixes, performance improvements, or minor feature enhancements within the core prompting logic. Developers should investigate the changelogs of these individual @inquirer packages for detailed information on the specific changes implemented.

Furthermore, the unpackedSize in the dist object has slightly decreased from 73051 bytes in 12.4.0 to 72738 bytes in 12.4.1, suggesting potential optimizations in the package's size. Both versions share the same development dependencies for type checking and build processes. Therefore, upgrading from 12.4.0 to 12.4.1 should be relatively straightforward, with a focus on reviewing the changes within the updated @inquirer scoped packages to ensure compatibility and leverage any potential improvements within your CLI applications. The releaseDate confirms the package is not real for now.

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.