Replies: 2 comments 4 replies
-
|
As of v2.0.2, it looks like the Alternatively, if you just use Either way, I'm going to close this since there is a solution now. |
Beta Was this translation helpful? Give feedback.
-
|
My lord. I love Vercel and use turborepo and Next almost daily, but that CLI decision must've come at 3am. That was a nightmare and made the log output pretty much useless. |
Beta Was this translation helpful? Give feedback.
-
|
yep, have the same problem and would really like an env var to turn this off |
Beta Was this translation helpful? Give feedback.
-
|
IMHO the new UI should never been the default in the first place. i tried to CTRL+C i tried so many things and i feel like "it just takes over". |
Beta Was this translation helpful? Give feedback.
-
|
I agree 100%. I'm trying to copy a JSON output from the logs and it doesn't allow me to by clicking and dragging the mouse. |
Beta Was this translation helpful? Give feedback.
-
|
@itechKaitoQueiroz did you try |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-goals
No response
Background
The new UI is great, but there are some cases where I would prefer to have the old, non-interactive UI. There is an option to disable it globally (https://turbo.build/repo/docs/reference/configuration#ui), but I don't want to disable it everywhere, just in certain scenarios.
Currently you can kind of work around this by piping the output into
cat, which forces the old ui, but you lose colors unless you also set theFORCE_COLORenv variable:This seems like a hacky workaround for what should be a configurable option.
Proposal
In addition to the global
uioption, allow it to be configured per-command via a CLI option like:And/or via an environment variable like:
Beta Was this translation helpful? Give feedback.
All reactions