#9215 wrangler d1 migration fails silently when executed in a directory without Wrangler config
Fixed in PR #11711 (merged 2025-12-19). D1 migration commands now show clear error when no config file present. Duplicate #11709 was closed by same PR.
Close as fixed by PR #11711
Analysis Report
Issue Review: cloudflare/workers-sdk#9215
Summary
D1 migration commands fail silently when executed in a directory without a wrangler config file.
Findings
- Created: 2025-05-12
- Updated: 2025-06-09
- Version: wrangler 4.14.4 -> 4.60.0
- Component: D1 / wrangler
- Labels: bug
- Comments: 3
Key Evidence
Issue confirmed and reproduced by maintainer: @jamesopstad confirmed the issue on 2025-06-09 and moved it to backlog.
Duplicate issue filed and fixed: Issue #11709 describes the exact same problem (running
wrangler d1 migrations applyin a non-worker folder gives no feedback) and was closed when PR #11711 merged.PR #11711 fixes this issue: Merged 2025-12-19, titled "fix(wrangler): show error when D1 migration commands run without config file". The fix shows a clear error message: "No configuration file found. Create a wrangler.toml or wrangler.json file to define your D1 database."
Fix is in changelog: The wrangler CHANGELOG.md includes the fix at line 466: "Show an error when D1 migration commands are run without a configuration file".
Fix is released: The fix is available in current wrangler versions (4.60.0).
Recommendation
Status: CLOSE
Reasoning: PR #11711 (merged 2025-12-19) explicitly fixes the silent failure issue for D1 migration commands. The fix has been released and is available in current wrangler versions. Issue #11709, which described the exact same problem, was correctly closed by the PR.
Action: Close this issue as fixed by PR #11711.
Suggested Comment
This has been fixed in PR #11711 (wrangler 4.17.0+). Running D1 migration commands without a wrangler config file now shows a clear error message:
"No configuration file found. Create a wrangler.toml or wrangler.json file to define your D1 database."
Please upgrade to the latest wrangler version (
npm install -g wrangler@latest) to get this fix. Closing as resolved.
Notes & Feedback (0)
No notes yet.