Improve error messages for CLI flags, type generation, auth scopes, dev server tunnels, and compatibility flags#14241
Conversation
🦋 Changeset detectedLatest commit: 1c3b0c5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
|
UnknownError: ProviderInitError |
|
@dario-piotrowicz Bonk workflow failed. Check the logs for details. View workflow run · To retry, trigger Bonk again. |
|
✅ All changesets look good |
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
The scope code is well-guarded ( Let me do a final scan: telemetry messages were preserved (good — AGENTS.md says they should be stable static labels, and they weren't changed even though wording changed). All static telemetry labels remain unchanged. I've reviewed all 13 files. The changes are:
No logic bugs, security issues, backward-compatibility violations, or incorrect API behavior. The only theoretical concern (scope set divergence) cannot occur in practice and would be a nitpick. LGTM |
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
…ev server tunnels, and compatibility flags
3010fa8 to
3d8c389
Compare
petebacondarwin
left a comment
There was a problem hiding this comment.
Codeowners Bypass
(KV is requested but this is a trivial change to error messages and not worth blocking on)
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Error messages across several areas now name the exact flags or values involved and suggest how to fix the problem:
demandOneOfOption(used by KV commands): messages now include--prefixes and clear "Missing required option" / "Conflicting options" phrasing instead of the vague "Exactly one of the arguments ... is required".wrangler types --include-env=false --include-runtime=false: the error now names both flags and explains what each does.wrangler login --scopes: invalid scopes are individually identified instead of dumping the entire array.wrangler dev --tunnel --remote: the error now explains why tunnels require local mode and suggests two concrete fixes.nodejs_compat_populate_process_env/nodejs_compat_do_not_populate_process_env,global_navigator/no_global_navigator): errors now name the specific conflicting flags.A picture of a cute animal (not mandatory, but encouraged)