LitoMore

I tried `inquirer@8` on both Command Prompt and PowerShell, and can't reproduce this issue on my Windows 11.

TBH, I think it's easy enough to wrap a `setTimeout` on the developers' side. It's not necessary to make this a base functionality.

A good project should be **simple and easy to use for everyone**. Take this `Timeout` feature as an example, we need to think about: - When the user sends keyboard...

@SBoudrias I just realize we now have no way to manually end the current prompt. Previously we can use `prompt.ui.activePrompt.done()` to set the prompt to `done`. But for our `@inquirer/prompts`,...

@andrisi For the old `inquirer`, you can use [`Promise.race`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/race) to implement this feature. ```javascript const prompt = inquirer.prompt(...); const defaultValue = new Promise(resolve => { setTimeout(() => { resolve(...) prompt.ui.activePrompt.done();...

We can change the documentation to `await setTimeout()` once we target our package with Node.js 16. See https://nodejs.org/api/timers.html#timerspromisessettimeoutdelay-value-options

@SBoudrias np. But we have already released a new major version of our package. The `"engines": ">=16"` change will be another breaking to our package. What do you think? Or...

Got it.

Hi @Kreijstal, @guillaume86. Simply import `npm:@inquirer/prompts` to your Deno project. See https://docs.deno.com/runtime/manual/node/npm_specifiers. Closing.

@SubJunk All `inquirer` related changes are in the `packages/inquirer` directory. So you can check its commit history: https://github.com/SBoudrias/Inquirer.js/commits/master/packages/inquirer. @SBoudrias We may still need to keep the release updated so our...