fix(wizard): Fix wizard workbench runs against local MCP/repo#641
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
sarahxsanders
left a comment
There was a problem hiding this comment.
pnpm try strikes again
9fcc815 to
6f1c211
Compare
Merge activity
|
| console.error('TUI init failed:', err); | ||
| } | ||
| // File-log first — the cleanup below can throw or exit. | ||
| logToFile('[run-wizard] FATAL:', err); |
There was a problem hiding this comment.
I will say to carefully consider what we log to the log file vs. just capture as a error using error tracking. Some of this shouldn't really be seen by an end user. There's nothing they can do with that info, and we can always get more info in error tracking, anyway.
(I think this is one example)
| // The console.error below is wiped with the alt screen; this survives. | ||
| logToFile('[screen-error-boundary]', error); | ||
| // eslint-disable-next-line no-console | ||
| console.error('[ScreenErrorBoundary]', error.message, error.stack); |
There was a problem hiding this comment.
Duplicate?
Maybe we should add error tracking to PostHog, too (or instead of the console log)

Problem
pnpm trydoesn't supportrequireand was dying instantly with no log traceChanges
requireif not availableTest plan