Workers SDK Issue Reports

← Back to Dashboard

#7288 🐛 BUG: Vitest inline snapshot does not get updated

Recommendation:KEEP OPEN
Difficulty:Windows-specific bug: vitest-pool-workers inline snapshots fail to update, line numbers report incorrectly, code coverage broken. Second user confirmed Oct 2025. No fix merged.
Reasoning:

Keep open - affects all Windows users of vitest-pool-workers

Suggested Action:

Yes

View on GitHub →

Analysis Report

Issue Review: cloudflare/workers-sdk#7288

Summary

Vitest inline snapshots do not update on Windows; the issue also causes incorrect line numbers in test results and code coverage.

Findings

  • Created: 2024-11-18
  • Updated: 2025-10-30
  • Version: 3.60.3 (Wrangler) → 4.60.0 (current)
  • Component: vitest-pool-workers (Workers Vitest Integration)
  • Labels: bug, vitest
  • Comments: 2

Key Evidence

  • Bug is Windows-specific (confirmed by reporter after testing on Ubuntu and Windows GitHub runners)
  • Affects multiple features: inline snapshots, test line numbers, and code coverage
  • Reporter states this makes testing "practically unusable on Windows"
  • A second user confirmed the issue on 2025-10-01 (still experiencing wrong line numbers)
  • No merged PR explicitly references fixing this issue
  • Changelog search found no mention of issue #7288 being fixed
  • PR #9348 "Fix E2E snapshots on Windows" was merged 2025-05-23 but is unrelated (E2E test infrastructure, not vitest-pool-workers)
  • Issue is over 14 months old with recent user confirmation (Oct 2025)

Recommendation

Status: KEEP OPEN

Reasoning: This is a legitimate Windows-specific bug that makes the Workers Vitest integration unreliable for Windows users. The issue affects multiple critical features (inline snapshots, line numbers, coverage). A second user confirmed the bug persists as recently as October 2025. No fix has been merged.

Action: Keep open. Consider prioritizing as it affects Windows developer experience significantly. The root cause may be related to path separator differences (backslash vs forward slash) or CRLF line ending handling in source maps.

Suggested Comment

Thank you for reporting this issue and for the detailed reproduction steps. We've confirmed this is still an open bug affecting Windows users. The issue appears to be related to how vitest-pool-workers handles source maps on Windows, causing incorrect line number mappings that affect:

  • Inline snapshot updates
  • Test result line numbers
  • Code coverage reporting

We're keeping this issue open for a fix. In the meantime, Windows users may need to run tests in WSL as a workaround.

Notes & Feedback (0)

No notes yet.

Add Note