Simon Boudrias
Simon Boudrias
Yeah, the problem is Node doesn't really allow running 2 readlines at the same time. So nesting your prompts make them conflict with each other. I don't know of any...
`validate` isn't supposed to prevent or replace input. That being said, it's possible something is wrong when we end up printing the number on the terminal. I do not think...
Hi, let's try to see what happens! 1. First, could you confirm you're using the latest version? Or which version you're using? 2. And could you try this in another...
I'm happy to review PRs starting on the new packages. I wanted to add TS, just doesn't have the time.
The first stab is launched over https://github.com/SBoudrias/Inquirer.js/pull/1112 - there's a fair amount of work, but I explained which files to focus on there. We can do them one by one!
@TDP17 that'd be great! I'll leave those to you for at least a week. Feel free to send an incomplete PR if you get stuck somewhere; that way I'll know...
I'm not quite sure what would be involved. But I think this could be complicated since Inquirer depends heavily on Node.js readline module.
All control flow can be done in your own JavaScript code. You can then just rely on Inquirer to display the relevant questions. ```js const { firstAnswer } = await...
PR welcomed. I think the default behavior should be updated to not clear the initial answer.
It's possible different prompts have different behaviors; or the stable version (`inquirer`) VS the beta ones (`@inquirer/input`). Any of this would explain the different behavior? Also anyone has strong opinion...