Oh, question since I'm there: is it planned to change the prefix to match cliui's style? Or to bake the prompts directly in cliui?

Thanks for the PR 😄

I believe, I will keep this module separate and not move it to cliui for now. No good reasons for it, but don't want to create more work for myself.

Regarding the prefix, can you point me to the exact code you are talking about?

Hey, thank you for the answer.

Here's what I call the "prefix":

And here's what I thought it would look like:

To change it I just extended Prompt from @poppinss/prompts/build/src/Base to override the prompt method and hardcode the option.prefix property.
They are originally defined in each reimplemented method from Enquirer (eg. Prompt#ask).

Okay. I am little bit confused. The prefix in cliui can have different values. Whereas with prompts we always want it to be a pointer so I think their design doesn't have to match. Lemme know if I am not getting it at all :)

When I mention the cliui prefix, I mean the [ level ] one, not the one that we can modify on the fly (eg. not logger.info('text', 'custom prefix')).

What I was initially wondering (and I worked around it, as shown in the screenshots) is if the prompts' pointers (that I called prefix, see first screenshot) were going to match cliui's actual prefixes (eg. [ question ], see second screenshot).

And you answered my question:

Whereas with prompts we always want it to be a pointer so I think their design doesn't have to match.

So, thank you. I could work around it anyway. :)

Cool. So we don't have anything more to change now. I will merge this PR. Thanks for taking out time for it 🙂