#8951 wrangler dev intermittently fails in docker container when registry is a mounted volume
Problematic file-registry.ts completely removed in PR #10245 (wrangler 4.32.0). Dev registry migrated to Miniflare. Code path causing ENOENT error no longer exists.
Close with comment explaining fix is in wrangler 4.32.0+
Analysis Report
Issue Review: cloudflare/workers-sdk#8951
Summary
wrangler dev fails with ENOENT error on utimesSync in file-registry.ts when running in Docker with mounted volumes.
Findings
- Created: 2025-04-15
- Updated: 2025-05-12
- Version: 4.7.1 → 4.60.0 (current)
- Component: wrangler (dev-registry)
- Labels: bug
- Comments: 1
Key Evidence
- Maintainer acknowledged: @edmundhung commented on 2025-05-12 that he would follow up with a fix
- Code deleted: The problematic file
packages/wrangler/src/dev-registry/file-registry.ts(line 105 mentioned in the error) was completely removed in PR #10245 - PR #10245: "Migrate wrangler dev to use Miniflare dev registry" was merged on 2025-08-19 by @edmundhung
- The entire
packages/wrangler/src/dev-registry/directory was deleted - Dev registry functionality moved to Miniflare
- Released in wrangler 4.32.0
- The entire
- Version gap: Issue reported against 4.7.1; fix released in 4.32.0; current version is 4.60.0
Recommendation
Status: CLOSE
Reasoning: The exact file and code path causing the error (packages/wrangler/src/dev-registry/file-registry.ts:105) no longer exists. It was removed as part of a complete refactor that migrated dev registry functionality to Miniflare in PR #10245, released in wrangler 4.32.0. The maintainer who acknowledged the issue (@edmundhung) is the same person who authored the fix.
Action: Close the issue with a comment explaining the fix.
Suggested Comment
This issue has been resolved. The problematic code in
file-registry.tswas removed as part of PR #10245, which migrated the dev registry implementation to Miniflare. This was released in wrangler 4.32.0.Please update to the latest version of wrangler (4.60.0+) and let us know if you still experience this issue. Thanks for reporting!