@inquirer/[email protected]

• Hoist peer-dependencies to remove warning when using yarn

[email protected]

• @types/node is now only a peerDependencies. This reduces the install size of inquirer dramatically for folks not using Typescript. It's unlikely to break your builds if you used TS already, if it does run npm install --dev @types/node/yarn add --dev @types/node.

@inquirer/[email protected]

• @types/node is now only a peerDependencies. This reduces the install size of inquirer dramatically for folks not using Typescript. It's unlikely to break your builds if you used TS already, if it does run npm install --dev @types/node/yarn add --dev @types/node.

[email protected]

• Now exports base utility Typescript types: import type { Question, DistinctQuestion, Answers } from 'inquirer';

You should use as follow to keep the inference working properly:

const questions = [
    { ... }
] as const satisfies Question[];
// If you're not using inquirer plugins, `Question` could alternatively be replaced by `DistinctQuestion` for stricter checks.

[email protected]

• Fix #1555: when behaviour changed unexpectedly when returning a falsy value.

[email protected]

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.

@inquirer/[email protected]

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.

@inquirer/[email protected]

• theme.prefix can now be defined per status: { idle: string; done: string; }
• theme.prefix changed the default prefix.done style to a tick mark (previously was the same ? as when idle.)
• theme.message now takes a second argument representing the status of the prompt; (message: string, status: 'idle' | 'loading' | 'done') => string
• Bump dependencies & an internal refactor of exit handlers.

[email protected]

• Fix the filter option not working.
• The signal: AbortSignal didn't work with class based prompts (OSS plugins.) Now it should work consistently with legacy style prompts.

[email protected]

• Fix expand prompt being broken if a Separator was in the choices array.