inquirer 14.x

Use Inquirer.js 14's legacy prompt API correctly, including v14 prompt registration behavior, prompt-module creation, separators, and interactive-terminal limitations.

For

inquirer@14.2.2

Verified

2026-09-08, 3 examples executed

Package

@modootoday/pmcp-inquirer@14.0.0

What it covers

• Scope and package shape
• The important v14 behavior change
• Asking questions
• Non-interactive environments
• Prompt modules
• Separators in choices
• Reactive questions
• Built-in prompt details and environment caveats
• Migration and v14 notes
• Not covered

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import inquirer from 'inquirer';
import assert from 'node:assert/strict';

assert.equal(typeof inquirer.prompt, 'function');
assert.equal(typeof inquirer.registerPrompt, 'function');
assert.equal(typeof inquirer.createPromptModule, 'function');
assert.equal(typeof inquirer.restoreDefaultPrompts, 'function');
assert.equal(typeof inquirer.Separator, 'function');

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. This is what happened, quoted from the run. The full ledger lists every package examined, including the ones that never became a skill.

• killed by the kernel at the memory limit our example

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-inquirer

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.