[workers-utils] Report a non-array queues.consumers as a config error instead of crashing

[LeSingh1]

validateQueues pushes the "should be an array" diagnostic for a non-array queues.consumers, but then iterates the value anyway — there is no else or early return. The diagnostic it just prepared never reaches the user.

With consumers: null:

TypeError: Cannot read properties of null (reading 'length')
    at src/config/validation.ts:5116

With consumers: "my-queue" the string is iterated character by character, so the real error is buried under one spurious diagnostic per character:

- The field "queues.consumers" should be an array but got "my-queue".
- "queues.consumers[0]" should be a objects, but got "m".
- "queues.consumers[1]" should be a objects, but got "y".
... (6 more)

Guarding the loop behind the array check lets the intended diagnostic surface on its own.

---

• Tests
  • Tests included/updated
• Public documentation
  • Documentation not necessary because: this corrects validation error reporting only; no config surface or API changes.

Note

This is a contribution from an AI agent: Claude Code (Claude Opus 4.5), working on behalf of @LeSingh1. Review comments will be read and responded to.

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 48f0137

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

This PR includes changesets to release 6 packages

Name	Type
@cloudflare/workers-utils	Patch
@cloudflare/autoconfig	Patch
@cloudflare/cli-shared-helpers	Patch
@cloudflare/deploy-helpers	Patch
@cloudflare/remote-bindings	Patch
@cloudflare/workers-auth	Patch

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

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15010

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15010

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15010

create-cloudflare

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

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15010

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15010

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15010

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: 48f0137

[jamesopstad]

Hi. We are not accepting PRs that don't have an associated issue. Please could you open an issue with a reproduction first. Thanks.

[LeSingh1]

Understood, and sorry — I should have read CONTRIBUTING.md more carefully before opening these. I'll write up an issue with a reproduction and link it here.

I have five more fixes in this repo staged locally. I've stopped filing them; I'll open issues for those instead and wait, rather than send more PRs.

[LeSingh1]

Issue with reproduction: #15069

[dario-piotrowicz]

Thank you very much for the fix (and the issue and everything) @LeSingh1 🙂

I've accepted devin's changeset suggestion, besides that all else looks good to me 😄 💪

[workers-devprod]

Codeowners reviews satisfied