Version Details and Security Vulnerabilities

📦

inquirer

12.1.0

Comparision Betweeen 12.1.0 and 12.0.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.05 KB

Version 12.1.0 Details

Inquirer.js is a popular npm package offering a suite of interactive command-line user interfaces. Comparing versions 12.1.0 and 12.0.1 reveals subtle but potentially important changes for developers. Both versions share the same core dependencies like rxjs, run-async, mute-stream, and ansi-escapes, crucial for asynchronous operations, managing output streams, and terminal styling. The primary differences lie in the updated versions of the internal @inquirer scoped packages.

Version 12.1.0 upgrades @inquirer/core from 10.0.1 to 10.1.0, @inquirer/type from 3.0.0 to 3.0.1 and @inquirer/prompts from 7.0.1 to 7.1.0. These updates likely incorporate bug fixes, performance improvements, and possibly new features within the specific prompt types and core functionalities of the Inquirer library. Developers should consult the changelogs for these @inquirer packages to understand the precise nature of these changes. Additionally, the @arethetypeswrong/cli in the devDependencies has received an upgrade from version 0.16.4 to 0.17.0 which is probably used to check type definitions. These upgrades suggest a focus on stability and feature enhancement across Inquirer's modular architecture.

For developers, upgrading to 12.1.0 may involve a careful review of the @inquirer package changelogs to ensure compatibility with existing code. However, the incremental nature of these version bumps suggests a low risk of breaking changes. The potential benefits include improved prompt handling, enhanced type safety, and access to new features within the individual prompt implementations. The update might be worth applying, especially to benefit from recent bug fixes.

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.