Disabling the tui causes issues
Current Behavior
setting tui enabled = false results in this output
the issue goes away if I remove this from all project.json files
"typecheck": {
"executor": "nx:run-commands",
"options": {
"command": "pnpm typecheck",
"cwd": "apps/webapp"
}
}
yet still run the command with pnpm exec nx run-many --target=typecheck --projects=@workspace/webapp,@workspace/backend
Expected Behavior
The UI should show the neat arrangement as expected without rendering issues
GitHub Repo
https://github.com/conradkoh/next-convex-starter-app/tree/nx-tui-issue
Steps to Reproduce
- Run pnpm run typecheck from the root
- You can see the rendering issue
- Revert the last commit
- Issue will be resolved
Nx Report
NX Report complete - copy this into the issue template
Node : 24.10.0
OS : darwin-arm64
Native Target : aarch64-macos
pnpm : 10.15.1
nx : 22.0.2
@nx/workspace : 21.4.1
@nx/devkit : 21.4.1
typescript : 5.8.3
---------------------------------------
Cache Usage: 0.00 B / 92.64 GB
---------------------------------------
The following packages should match the installed version of nx
- @nx/[email protected]
- @nx/[email protected]
To fix this, run `nx migrate [email protected]`
Failure Logs
Package Manager Version
pnpm 10.15.1
Operating System
- [x] macOS
- [ ] Linux
- [ ] Windows
- [ ] Other (Please specify)
Additional Information
No response
I'm experiencing the same issue and it's significantly impacting my workflow. I disabled the new TUI because it doesn't provide any value to me, but now the logs are difficult to read due to the formatting issues. Either way, the terminal output is hard to work with. Would really appreciate a fix for this.
hi guys, traced this further and managed to be more specific about the cause. I do not see this issue when running commands with the flag --outputStyle=dynamic but experience it when I set it to --outputStyle=dynamic-legacy.
I'm seeing the same issue, also with the run-many command.
It's not consistent and only about 50% of the devs on my team are seeing it, but it does occur regularly and it's very disruptive.
It repros for a few different targets so it's probably not related to any specific commands/tools being run (e.g. tsc, lint, etc.)