Snippet typechecking (snippet:types) silently passes / fails to run on Windows

[Adityakk9031]

Describe the bug

When running leadtype lint on Windows, TS/JS code snippet typechecking silently passes even when snippets contain compile/type errors. This happens because the virtual compiler host looks up virtual files using normalized paths (forward slashes /), while the virtual file cache keys are stored with mixed separators.

Steps to reproduce

1. On Windows, create a document containing a TS code block with a type error (e.g. greet(42) where it expects string).
2. Run leadtype lint (or run vitest on packages/leadtype/src/lint/snippet-typecheck.test.ts).
3. Observe that the typechecking violations are not caught and the command returns exit code 0.

Cause

In packages/leadtype/src/lint/snippet-typecheck.ts, virtualDir is resolved via projectRoot (using Windows backslashes \), and the file name is joined using /:

const virtualDir = `${projectRoot}/.leadtype-snippet-${index}`;

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[coderabbitai]

🔗 Related PRs

#34 - Fix Leadtype CLI symlinked bin execution [merged]
#130 - Make leadtype lint config-aware [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!