Quick question if I may, but will queues
Quick question if I may, but will queues eventually add support for remote dev?
Currently any worker that makes use of queues still isn't able to make use of things like quick edit, edge preview, remote dev, etc
4 Replies
We do want to for sure - it's been a very common ask! And as you noted, remote dev is such a common part of the workers dev workflow
But given how push consumers on Queues work (ie: queues invoke your consumer worker with a batch of messages) full remote support is a tough one to get right. still on our roadmap though, and definitely something I'd like us to support soon
Yeah totally understandable. I just wish that at least it wouldn't fully break edge previews/remote, and instead that any queue-related calls would result in a no-op instead, so people could at least test their fetch handlers for example
It's one of the main reasons why I try to avoid adding queues whenever possible, as trying to add them to any (existing) worker will break quick edit completely, and all requests you do in it give a arbitrary error that doesn't explain that it's happening because of queues.
I very frequently use quick edit / remote dev for rapidly debugging issues in prod, so losing this feature is a massive issue. I would be totally fine with the queue API being noop
+1 to this, noop with a log is already a big improvement over what we have today. we have to deploy to actually test (because other bindings don't have local)
For sure, that's a great suggestion. I really appreciate the candid feedback here! let me see what we can do 🙂