Simon Boudrias

@LitoMore honestly I think it's pain from the environment. I ran into multiple issues migrating Inquirer to ESM; it's not easy on Node.js - even though I know it works...

Today you can use the `validate` function for this, check the input and make sure there is content; if not return an error message. I'm leaning towards not augmenting the...

This might be an issue with the underlying modules handling external editors: https://github.com/mrkmg/node-external-editor

Hey @jamespohalloran, I made some progress on documenting the new core API over here https://github.com/SBoudrias/Inquirer.js/tree/master/packages/core - I'd love feedback and/or PRs helping to make that documentation better!

> Aside from that, honestly I don't believe that Yeoman's choice of using EJS is the best one, since Yeoman doesn't care about performance (nor should it), and there are...

@comatory could you just `console.log` before calling `inquirer.prompt` (and maybe just split in 2 `prompt` calls)?

@rizzlesauce that's possible; but closing the readline on windows was making the prompt unresponsive. The best solution on the longer term is probably moving away from rxjs altogether. I've made...

@nanomosfet take a look at the `@inquirer/*` prompts (https://github.com/SBoudrias/Inquirer.js/tree/master/packages/input and the other). They're simpler interfaces and should be faster. All core prompts are already re-implemented in that fashion, checkout the...

Yeah, `rxjs` has been a problematic dependency for memory leaks. Like I said, the new prompts under the `@inquirer/*` namespace aren't relying on it for this reason; and they're available...

Over here: https://www.npmjs.com/search?q=%40inquirer