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

[Request] Plain line output for spinner and progress in CI

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

Los mantenedores suelen responder en 1 día

@webywz ya está trabajando en esto.

Desde el 30/10/2026.

  • #632 de @webywz — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli

Línea de trabajo

Start by reading the implementations of spinner(), progress(), block() and the other live components in the repository, then trace how they detect CI and TTY output. The issue describes the desired plain-line behavior and final status lines; check existing component tests and add coverage for CI and non-TTY output. Done means logs contain no cursor codes, spinner frames or progress bars.

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

Descripción

Is your feature request related to a problem? Please describe.

When CI is "true", spinner() and progress() stop the animation. But the CI log still gets
terminal output that only makes sense on a TTY. This is the output of changeset publish
(changesets uses progress()) on GitHub Actions, with CI=true:

^[[?25l◒  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Publishing packages...
^[[1G^[[J◇  Successfully published:
...
^[[?25h^[[?25l◒  Creating git tags...
^[[1G^[[J◇  Created git tags.
^[[?25h

Progress updates also print lines like this one, with a new frame each time and no message:

◐  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

The problems:

  1. Cursor codes: ESC[?25l and ESC[?25h from block(), and ESC[1G with ESC[J from the
    clear step. A CI log viewer shows them as noise.
  2. The spinner frame (◒, ◐) on each line. A frame of an animation means nothing in a log.
  3. The progress bar. Each update prints one more bar line, often with no message.
  4. Each change of the spinner message prints a new line. That is fine for real steps, but a
    message that only updates a counter or a string fills the log.

Describe the solution you'd like

In CI mode (or when the output is not a TTY), spinner(), progress() and the other live
components write plain lines only:

  • No cursor or erase codes, and no call to block() that hides the cursor.
  • No spinner frame and no progress bar. Print the message, then the final status line
    (◇ Done, ■ Cancelled, ▲ Failed).
  • Optional: an option to skip message updates in CI, so only the start and the end lines print.

Describe alternatives you've considered

  • Strip ANSI codes in each consumer, for example with a pipe through sed. Every CLI that uses
    clack must then do it, and a pipe can hide the exit code.
  • #286 (use isTTY for isCI). That changes when CI mode turns on. This request is about what
    CI mode prints. Both changes work well together.

Additional context

  • @clack/prompts 1.8.1, @clack/core 1.5.1, through @changesets/cli 3.0.3.
  • Node 26, GitHub Actions runner.
Lenguaje dominante
TypeScript
Estrellas
8.1k
Forks
225
Merge medio
12 h 54 min
PR fusionados (30 d)
3

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.