How to develop with both Browser Rendering and Queues?
I'm working on an app that is using both Browser Rendering and Queues to manage requests to the browser rendering workers, but I can't run the browser rendering workers locally, and if I try to use remote dev it fails to boot if I have any queues defined in wrangler.toml https://developers.cloudflare.com/workers/testing/local-development/#supported-resource-bindings-in-different-environments
Right now I've removed the queue and run the browser worker directly, but this will not work well in prod. Is there a solution to this?
Cloudflare Docs
Local development | Cloudflare Workers docs
Develop your Workers locally via Wrangler.
1 Reply
I am also trying to call the browser renderer in a workflow and this is not working in remote dev either :\
Any guidance on how I can structure this would be very welcome 🙏
I have unblocked myself by factoring the browser rendering work out to a separate worker, and calling the production instance of it in the rest of my app when developing locally. This complicates my deployment, but let's me continue to work.
It would be really nice if local development could talk to real browser rendering instances so that this isn't necessary, similar to what Vectorize does