fix(wrangler): show error when D1 migration commands run without config file

[southpolesteve]

Fixes #11709.

Previously, running wrangler d1 migrations apply, wrangler d1 migrations list, or wrangler d1 migrations create in a directory without a wrangler.toml or wrangler.json file would silently exit with no feedback, leaving users confused about what went wrong.

Now these commands display a clear error message:

"No configuration file found. Create a wrangler.toml or wrangler.json file to define your D1 database."

Written using OpenCode and Claude Opus 4.5

Prompt: "Can you solve this issue for me #11709"

---

• Tests
  • Tests included/updated
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: This is a bug fix that adds an error message; no new features or API changes
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: Not a patch change to stable V3; this is a UX improvement for current version

[changeset-bot]

🦋 Changeset detected

Latest commit: 7d64a96

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[claude]

Claude finished @southpolesteve's task —— View job

---

Reviewing Changeset

• Read changeset guidelines
• Review changeset file
• Validate and report findings

---

✅ All changesets look good

The changeset .changeset/itchy-squids-design.md passes all validation checks:

1. Version Type: ✅ Correctly uses patch for a bug fix (adding error messages)
2. Changelog Quality: ✅ Has a clear title and detailed body explaining:
   • What the bug was (silent exit with no feedback)
   • Which commands are affected
   • What the new behavior is (clear error message with exact text)
3. Markdown Headers: ✅ No h1/h2/h3 headers present
4. Error Message Accuracy: ✅ The error message in the changeset matches the implementation exactly

The changeset accurately describes the change and provides good context for users reading the changelog.

---

[github-actions]

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main issue-11709 might be a good starting point.

Notes:

• your PR branch should be named v3-backport-11711
• add the skip-v3-pr label to the current PR to stop this workflow from failing

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11711

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11711

miniflare

npm i https://pkg.pr.new/miniflare@11711

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11711

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11711

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11711

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11711

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11711

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11711

wrangler

npm i https://pkg.pr.new/wrangler@11711

commit: 7d64a96