fix(cloudflare): use queue dev.id for consumer resource ID in local dev mode

[xiaoyu2er]

Problem

In local dev mode, Queue resources return an empty string for id (Cloudflare API ID) since no remote API call is made. When a Worker has multiple eventSources, all QueueConsumers are derived as ${queue.id}-consumer which all resolve to "-consumer", causing concurrent Promise.all writes to the same state file.

This leads to:

• Corrupted JSON state files (null bytes from concurrent writes)
• Silently broken queue consumers — Worker HTTP endpoint responds normally but queue messages are never consumed
• Persistent failures — every subsequent alchemy dev fails with SyntaxError: JSON Parse error

Fix

Use queue.dev.id (the resource ID, e.g. "email-queue") in local dev mode instead of queue.id (empty ""). The dev.id is always unique per queue and available in dev mode.

// Before: all consumers get ID "-consumer"
QueueConsumer(`${eventSource.queue.id}-consumer`, { ... });

// After: each consumer gets unique ID like "email-queue-consumer"
const queueId = options.local
  ? (eventSource.queue.dev?.id || eventSource.queue.id)
  : eventSource.queue.id;
QueueConsumer(`${queueId}-consumer`, { ... });

Reproduction

See #1363 for full details and a diagnostic script.

Quick summary: any Worker with 2+ eventSources in alchemy dev mode will have all queue consumers writing to the same -consumer.json state file.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/alchemy@1364

commit: f08822f

[Mkassabov]

wouldn't we want this the other way around?

const queueConsumerId = options.local
              ? eventSource.queue.id ?? eventSource.queue.dev?.id
              : eventSource.queue.id;

or if we know that the non-dev queue id is always going to be bad just

const queueConsumerId = options.local
              ? eventSource.queue.dev?.id
              : eventSource.queue.id;