Open alexeira opened 4 months ago
Dup of #10592 ?
It seems that it is the same type of error, even so, I emphasize again that it also happened to me when pressing C^c
and that it was in Windows 11.
Also that since version 1.1.16 onwards, the error has not reappeared.
What version of Bun is running?
1.1.12+43f0913c3
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
I usually get this error after doing a C^c to finish a simple
bun run --watch index.ts
script, I have the suspicion that it is something fromPSReadLine
, but not having so much knowledge I don't know if the problem comes from there.I have tried disabling
PSReadline
and I still get this error.It also usually happens just after doing a
bun -h
and just waiting a few seconds or typing any key.What is the expected behavior?
Not an error, I hope to continue with the development cycle.
What do you see instead?
Additional information
Certainly it could be a
crash
error, but as it is not a bun error as such but an unexpected behavior of the terminal I place it asbug
and not ascrash
.I want to note that when using the
pwsh
terminal invscode
I don't get this error.