Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug] Prompts never settle when stdin ends

Abierto
  • ¿Algo no está bien?
#615 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli

Línea de trabajo

The hang comes from prompt() in packages/core/src/prompts/prompt.ts, which settles only on submit and cancel (around lines 185-196), so start there and look at how the input stream is wired in. Reproduce with node repro.mjs < /dev/null using the snippet in the issue. Done means a prompt whose input ends (or has already ended) resolves with the cancel symbol, and both repro runs print 'settled with cancel' and exit 0. Check first that maintainers agree on cancel as the behaviour, since the reporter has asked.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Environment

  • OS: macOS
  • Node Version: v22.23.2 and v26.0.0
  • Package: @clack/core (through @clack/prompts)
  • Package Version: @clack/prompts 1.8.1, @clack/core 1.5.1, same on main (5ac9e73)

Describe the bug

When stdin ends while a prompt is waiting, or before it starts, the prompt never settles. await confirm(...) hangs, and in an ES module Node then exits with code 13 ("Detected unsettled top-level await"), with the cursor still hidden. It happens with closed stdin (< /dev/null, some CI runners and agent shells) and with piped input that runs out before the last prompt.

prompt() resolves only on submit and cancel (prompt.ts#L185-L196), and nothing handles the input stream ending.

To Reproduce

// repro.mjs
import { confirm, text, isCancel } from '@clack/prompts';

const ok = await confirm({ message: 'Continue?' });
console.log('confirm settled with', isCancel(ok) ? 'cancel' : ok);
const name = await text({ message: 'Name?' });
console.log('text settled with', isCancel(name) ? 'cancel' : JSON.stringify(name));

$ node repro.mjs < /dev/null
◆  Continue?
│  ● Yes / ○ No
└
Warning: Detected unsettled top-level await at file:///.../repro.mjs:3
$ echo $?
13

$ printf 'y\r' | node repro.mjs
◇  Continue?
│  Yes
confirm settled with true
◆  Name?
│  _
└
Warning: Detected unsettled top-level await at file:///.../repro.mjs:5
$ echo $?
13

Expected behavior

The prompt settles when its input ends. Returning the cancel symbol seems the natural fit, since no answer can come and callers already handle isCancel(). With that, both runs above print "settled with cancel" and exit 0.

Additional Information

I've read #533 and the advice to skip prompts when there is no TTY. This is narrower: a prompt can still be reached with closed or piped stdin, and then it hangs with no message instead of cancelling. We hit it with @fumadocs/cli add in a non-interactive shell: it wrote the files, asked "Do you want to install with npm?", and exited 13 without installing anything.

I have a small fix in @clack/core with tests (cancel on the input's end, and right away if the input has already ended) and can open a PR if cancel is the behaviour you want.

Lenguaje dominante
TypeScript
Estrellas
8.1k
Forks
218
Merge medio
1 d 10 h
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de bombshell-dev/clack

Todos los issues de bombshell-dev/clack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.