NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #1262 most downloaded on npm
Inquirer confirm prompt
Latest stable
6.4.0
Last release 12 days ago
10 Nov 2026
Release timing varies
gaps range from 8 days to 3 months
Some releases are documented
notes for 16 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
130 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
The single keystrokes y/n are now always accepted, even when localized keywords (e.g. Chinese 是/否) are configured — theme keywords keep precedence whe
y/n are now always accepted, even when localized keywords (e.g. Chinese 是/否) are configured — theme keywords keep precedence when matching (#2281, closes #2279).@inquirer/type bumped to ^4.2.0 — new withResolver export (#2291)Your coding agent can read these notes before it upgrades. Set up the MCP server →
confirm() now trims surrounding whitespace from answers before matching yes/no keywords, so values such as yes — accidentally typed or piped into the
confirm() now trims surrounding whitespace from answers before matching yes/no keywords, so values such as yes — accidentally typed or piped into the prompt — no longer silently fall through to the default (#2254).@inquirer/core bumped to ^12.0.3 — fixes same-tick keystrokes reaching handlers of settled prompts (#2255)Nothing published for this version
Localized yes/no answers are now accepted and matched per-locale (e.g. Spanish s for sí, French o for oui, Chinese 是/否), instead of only English y/n.
s for sí, French o for oui, Chinese 是/否), instead of only English y/n. A new keywords theme property ({ yes, no }) is the source of truth for both parsing and display, with prefix-based, case-insensitive matching and the default answer marked in the hint.@inquirer/core bumped to ^12.0.1@inquirer/type bumped to ^4.1.0Accept explicit undefined as the default value
undefined as the default value (#2182)@inquirer/core bumped to ^12.0.0Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
No technical breaking changes; but we changed the style of the question prefix once the answer is provided. Once a question is answer, the prefix beco…
No technical breaking changes; but we changed the style of the question prefix once the answer is provided. Once a question is answer, the prefix becomes a tick mark (previously it was the same ? as when the prompt is idle.)
This is theme-able, and so can be overwritten to with theme.prefix.
usePagination now requires pageSize to be passed in. The size of the pages should inform the help shown on the screen, and keeping this information in 2 areas leave a change the default value will mistmatch.number.transformer option now receive { isFinal } as a flag to allow transforming the final answer differently.name as default message if message isn't provided.password prompt.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix Unix yes not properly being processed by the confirm prompt. (yes | node confirm-script.js)
yes not properly being processed by the confirm prompt. (yes | node confirm-script.js)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Surrounding whitespace in answers is now ignored, so values such as yes — accidentally typed or piped into the prompt — no longer fail to match (#2280
Nothing published for this version
@inquirer/core bumped to ^12.0.1
@inquirer/core bumped to ^12.0.1@inquirer/type bumped to ^4.1.0No source changes.
@inquirer/core bumped to ^12.0.0
@inquirer/core bumped to ^12.0.0No source changes.
@inquirer/core bumped to ^12.0.1@inquirer/type bumped to ^4.1.0No source changes.
@inquirer/core bumped to ^12.0.0
@inquirer/core bumped to ^12.0.0No source changes.
@inquirer/core bumped to ^12.0.0No source changes.
Nothing published for this version
Feat: Added a loading message while validating input. Customizable through a theme option.
transformer option to the input prompt allowing you to modify the displayed user input. (Useful to modify colors as user type, etc)Nothing published for this version
Fix: breaking change wrongly removed the Separator export.
Separator export.useEffect body. See #1307This decision was made to disambiguate what breaks in each package - with prompts re-exporting core, any core breaking change (no matter how minor) ca…
@inquirer/core isn't exported from @inquirer/prompts anymore. If you want to create custom prompts, import from the core package. This decision was made to disambiguate what breaks in each package - with prompts re-exporting core, any core breaking change (no matter how minor) caused a major version bump. Now only prompts interfaces breaking changes will be major on prompts. We're hoping this will simplify your usage of @inquirer/* packages.validate config; but it was rarely used. It's been removed and prompts relying on it are expected to handle it on their own (no default value.) The types were updated accordingly and will raise issue if you're using typescript.AsyncPromptConfig, it's been deprecated in favour of PromptConfig- import type { AsyncPromptConfig } from '@inquirer/core';
+ import type { PromptConfig } from '@inquirer/core';
- type Config = AsyncPromptConfig & { custom: 'value' };
+ type Config = PromptConfig<{ custom: 'value' }>;
Note: Old interface works for now, but is marked as deprecated.
Breaking: Upgrade to RxJS v5 which updates a bunch of Reactive interface method names.
For people not using the Reactive interface directly, this new major release should just work out of the box.
Update dependency to fix a LGPL license issue.
All prompts are now themable. See each prompts documentation about the options available.
message option of each prompt must now be a string. It could previously be an asynchronous function. See recipes for a migration option.Major rewrite of the core to rely on node's async hooks for better isolation of each prompts. Relying on this means each prompt context is fully isolated (previously it would rely on the module level context.)
We expect this update to be transparent to most. Though some custom event handlers within useEffect could stop working. If you find any issues there, first please let us know - there might be thing to improve internally to make it transparent. The manual fix will likely be to explicitly define events callback as an AsyncResource.
Let us know how this works for you!
The core codebase went through a major es5 to 6 refactor. As such, we're dropping support for Node 4.
This change will likely require changes to the community Plugins as es6 classes are enforcing more restriction (like constructor can only be invoked with new).
list, expand and rawlist prompts now accepts the value as default (previously it would only accept the choice index).fix: e2e testing utility now gracefully fail if a dependency isn't in the dependency tree (useful for things like strict Yarn PnP)
{ default: fn() }theme.style.keysHelpTip.theme.keybindingsdefault handling:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.