Back to Explore

SBoudrias/Inquirer.js

GitHub
10 updates · last 90 days1 watchersOpen source

Last release: 1 week ago

Inquirer.js is a JavaScript library for building interactive command-line user interfaces, providing common prompt types like input, select, checkbox, confirm, search, password, and editor. It is useful for creating terminal experiences that collect user responses with a consistent API and supports localization via the @inquirer/i18n package.

Project status

  • Active maintenance: The upstream GitHub repository has recent activity (last push on 2026-06-06), and the npm ecosystem shows multiple inquirer-related updates in late May 2026.
  • Update cadence: Updates appear clustered around 2026-05-29 to 2026-05-31 (in quick succession), with additional upstream activity on 2026-06-06, suggesting ongoing maintenance rather than a long period of inactivity.

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • @inquirer/prompts@8.5.2

    1 week ago

    Release @inquirer/prompts@8.5.2 is documented as a security-oriented fix related to the external editor integration. The code diff shows more than warning fixes, including changed temp file/directory handling and different error behavior when the configured editor cannot be started.

    Security
  • inquirer@14.0.2

    1 week ago

    inquirer 14.0.2 is a maintenance release that addresses security warnings related to the external-editor integration. No other user-facing changes are described in the release notes.

    Security
  • @inquirer/prompts@8.5.1

    1 week ago

    This release (@inquirer/prompts 8.5.1) rolls back the `mute-stream` dependency from v4 to v3 and adds internal tooling to prevent the same issue from recurring. The monorepo also updates Node engine range minimums (notably the lower Node 20 bound) to match what is already enforced by the project setup.

    Breaking
  • inquirer@14.0.1

    1 week ago

    This release of inquirer@14.0.1 rolls back the `mute-stream` dependency from v4 to v3, specifically to undo a previously introduced break related to `engines` compatibility. It also adds tooling to prevent regression of that dependency change, and adjusts the explicit `engines` limits to match what is already enforced by the minimum required state.

    Breaking
  • @inquirer/prompts@8.5.0

    1 week ago

    This release of @inquirer/prompts@8.5.0 adds support for enabling vim or emacs navigation keybindings via the INQUIRER_KEYBINDINGS environment variable, with select disabling its type-to-search behavior when vim bindings are enabled. It also fixes a cursor positioning bug related to terminal line wrapping, and bumps dependencies.

    Features
  • inquirer@14.0.0

    1 week ago

    Inquirer 14.0.0 introduces a behavior change where it will now throw an error when it encounters a prompt type that is not registered, making broken code easier to detect. It also adds optional vim/emacs keybindings via an environment variable, along with a cursor-positioning bug fix for line wrapping.

    BreakingFeatures
  • @inquirer/prompts@8.4.3

    4 weeks ago

    Release @inquirer/prompts@8.4.3 primarily fixes a Windows terminal cursor/rendering issue and improves TypeScript typing behavior for `choices` literal unions and `input` prompt defaults (including explicit `undefined`). It also bumps a set of internal dependencies across the inquirer monorepo to pick up those changes.

  • inquirer@13.4.3

    4 weeks ago

    This release focuses on bug fixes and TypeScript typing correctness in inquirer. It also bumps dependencies without specifying versions in the release notes.

  • @inquirer/prompts@8.4.2

    1 month ago

    This patch release for @inquirer/prompts focuses on fixing a Windows-specific terminal freeze where the prompt would stop reacting to keypresses. The code changes show the fix was implemented by changing when output is muted relative to readline initialization.

  • inquirer@13.4.2

    1 month ago

    This release of inquirer fixes an issue where some Windows terminals could freeze and stop responding to keypresses. The change is focused on restoring interactive input behavior on affected Windows environments.