Select the entire multi-line error pyramid
TypeScript reads top-down from outer wrapper types to the inner property failure, while Rust puts key borrow notes (`help:` and `note:`) at the bottom. Highlight the full diagnostic block.
How to decode TypeScript and Rust compiler errors without leaving your browser.
Highlight deeply nested TypeScript generic errors or Rust borrow-checker diagnostics on GitHub, CI logs, or docs and get an instant plain-English fix in place.
Best fit
Best for developers debugging TS2322/TS2345 generic pyramids or Rust ownership/lifetime diagnostics in GitHub Actions, Vercel logs, and documentation.
On-screen walkthrough
How this looks on a real webpage.
Instead of switching tabs and rebuilding context, highlight the exact passage that slowed you down and press your shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on macOS, fully customizable in settings).
1. Highlighted on page (GitHub Actions CI Log — TypeScript 5.6 Build Output)
error TS2322: Type 'Promise<{ id: string; status: string; metadata: Record<string, unknown>; }>' is not assignable to type 'Promise<WebhookResult>'. Type '{ id: string; status: string; metadata: Record<string, unknown>; }' is not assignable to type 'WebhookResult'. Types of property 'status' are incompatible. Type 'string' is not assignable to type '"delivered" | "queued" | "failed"'.
Ctrl+Shift+X“What is the root cause of this TS2322 error and what is the cleanest fix without using any?”
2. Vezz me on-screen answer overlay
1. **Root cause**: Your function returns a widened `status: string`, whereas `WebhookResult` requires the narrow literal union `"delivered" | "queued" | "failed"`.
2. **Fix for literal objects**: Add `as const` to the status property (e.g., `status: "delivered" as const`) or use `satisfies WebhookResult` on the return object.
3. **Fix for external inputs**: Narrow the string with a Zod enum or type guard before returning instead of casting with `as any`.
3. Suggested follow-up questions in thread
- “Show me the cleanest type guard function for narrowing `status`.”
- “Why did TypeScript widen `status` to `string` in the first place?”
Step-by-step workflow
How to run this workflow in place.
Press Ctrl+Shift+X and ask for the leaf mismatch
Ask Vezz me which single inner property, generic constraint, or lifetime parameter actually failed so you can ignore 30 lines of wrapper types.
Request a strict, idiomatic fix
Use our Senior Engineer Code Reviewer preset to get a type-safe fix (`satisfies`, discriminated union narrowing, or borrowing `&[T]`) rather than `as any` or `.clone()` spam.
Key details
Why this approach works better than switching tabs.
Comparison Matrix
Compiler Error Debugging Workflows
Comparing in-page selection against tab-switching and generic error-code searches.
| Approach | Strengths | Tradeoffs |
|---|---|---|
| Vezz me on CI / Docs Tab | Immediately isolating the inner leaf mismatch right beside your build log | Requires highlighting the full multi-line error block |
| Searching error code (e.g. TS2322 / E0382) | Learning the general definition of the compiler diagnostic | Too generic—TS2322 covers thousands of unrelated type mismatches |
| Copy-pasting into a separate chat tab | Long multi-file refactoring sessions | Loses surrounding PR diff and build-log context |
Frequently asked questions
Common questions about compiler error workflow.
Does Vezz me work inside GitHub Actions raw log viewers?
Yes. Any selectable text inside GitHub Actions step logs, Vercel build output, or raw log files can be highlighted and analyzed with Ctrl+Shift+X.
Can I include the failing function code along with the error?
Yes. If the error and code snippet are near each other on the page, highlight both together, or paste the error into the prompt box while highlighting the code.
How do I stop the AI from suggesting 'as any' or '@ts-ignore'?
Import our Senior Engineer Code Reviewer preset, which explicitly instructs the AI to preserve strict type safety and avoid unsafe casts.
Related workflows & guides
Explore connected pages.
Ready to try this workflow on your own reading?
Install Vezz me free, highlight text on any webpage, and press your customizable shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on Mac) to get an answer right beside the source.
