You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] When starting a spinner, the process won't stop after your script is done executing. #348
this makes sense as there's nothing we can listen for. an exit won't happen because the spinner is still iterating on a timer in the background, so there's no exit event to catch.
if something forcefully exits, the spinner does stop.
but you really should call stop()
its the same as if you had a setInterval running in your code somewhere, it'll never exit if you don't clean it up.
if you are calling stop, please provide an example as i can't reproduce that
The same is also happening with progress when using Deno.
import{progress}from'@clack/prompts'constspin=progress()spin.start('Hello')spin.stop('World')// process.stdin.unref?.(); // this is needed to exit with Deno
Activity
43081j commentedon Jul 1, 2025
do you mean you didn't call
stop()?this makes sense as there's nothing we can listen for. an exit won't happen because the spinner is still iterating on a timer in the background, so there's no exit event to catch.
if something forcefully exits, the spinner does stop.
but you really should call
stop()its the same as if you had a
setIntervalrunning in your code somewhere, it'll never exit if you don't clean it up.if you are calling
stop, please provide an example as i can't reproduce thativands commentedon Jul 3, 2025
I mean after calling stop
43081j commentedon Jul 3, 2025
do you have an example?
i've tried this locally and it works fine, so i think we will need a reproduction from you
ivands commentedon Jul 3, 2025
Yeah, so I just tried it on Node and it seems to work.
But in Deno it will get stuck.
However, i also had instances where my cli tool running in node would get stuck.
Just not sure now if the spinner was the problem anymore XD
43081j commentedon Jul 3, 2025
i also can't reproduce that in main, so i wonder if its a long gone problem
can you try out 1.0.0-alpha.1 and see if it still happens? so we at least know if its been fixed in latest
mikkelal commentedon Feb 23, 2026
The same is also happening with progress when using Deno.
Deno Version: v2.6.10
Package Version: 1.0.1
Seems like this related to this Deno issue: denoland/deno#30075 (comment)
43081j commentedon Feb 24, 2026
yup this sounds like a deno bug.
the original bug in this thread also has no repro in 1.x, so im going to close this.
we do clear all timers and such on exit fyi.