Replies: 2 comments 8 replies
-
|
Do you have a reproduction of this case you could share? |
Beta Was this translation helpful? Give feedback.
-
|
It sounds like you might want |
Beta Was this translation helpful? Give feedback.
-
|
That keeps the other tasks running, but once they finish, it'll quit the TUI. I'd prefer to stay in it even once its finished. |
Beta Was this translation helpful? Give feedback.
-
|
Re-reading again, it's sounding like you're looking for Watch Mode: https://turbo.build/repo/docs/crafting-your-repository/developing-applications#watch-mode This would mean a change to the errored package or app or its dependencies would get a retry when you edit source code and the whole of the |
Beta Was this translation helpful? Give feedback.
-
|
I'll try continue with watch when I get some time, and see if it's what I'm looking for. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, it looks like |
Beta Was this translation helpful? Give feedback.
-
|
I have the same concern 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried |
Beta Was this translation helpful? Give feedback.
-
Goals
Non-goals
Background
I use turbo as a better run-pty.
Proposal
The main thing I've missed since switching to turborepo is the ability to see errors in the TUI. Once there's an error, turborepo quits. Now that's a TUI, would it be possible to keep it open rather than printing them? I'd like to keep the TUI open after an error, and ideally be able to restart failed tasks if they just flaked or I've fixed them. It's jarring when I'm inspecting a result or status and then something fails. It would also be nice if the other tasks kept running, but that's probably out of scope for this particular request.
I don't know Rust, but this does bother me enough I'd be willing to give it a shot sometime if y'all decide this is worthwhile.
Beta Was this translation helpful? Give feedback.
All reactions