[Bug] `text` validate function for text when value is empty with default value

[pedrofcarvalho]

Environment

• OS: macOS
• Node Version: 22.5.1
• Package: @clack/promts
• Package Version: 0.11.0

Describe the bug
When calling the text's validate function without user input but with a default value defined, it should use the default value instead of relying solely on user input.

To Reproduce

• Link to reproduce with steps included

Steps to reproduce the behavior:

1. Open repro link
2. Run node index.js
3. Don't type anything, just press [Enter]
4. See behavior described on terminal

Expected behavior
Clear use case example:

CLI dev creates a text step for user to enter a path as input. There's some predefined value that CLI dev established to be the default use case for most users, but still allowing for that value to be changed.
Currently, the user would have to type/copy that entire path, causing a terrible user experience.

Fix Recommendation (starting a convo)
I see 2 possible ways to fix this:

1. Keep validate as is and add a check to the value on core/prompts/text - link to draft PR
2. Add a second optional argument, which would be the default value to validate. That way, Devs would have another quick option when using the validate function, without adding extra checks to the core library.

My goal with this section is to start a conversation and introduce my ideas about this issue, not a way for me to impose how I think things should be.
This would be my first contribution, so I'm pretty new here. Let me know what you think and hopefully let's get this fixed!

[43081j]

this may be a documentation issue rather than a bug

basically, a text prompt has:

• defaultValue - the value the prompt will default to on submission (assuming the user didn't type anything in)
• initialValue - the value the prompt will initially have

these are 2 different options because you might want the prompt to visually look like you left it empty, and yet default to a value behind the scenes (defaultValue is for that).

the latter is if you visually want a default value, and the user can change that

[chouchouji]

Maybe you should set initialValue to replace defaultValue.