Service Binding: local dev method
Hi, I'm developing 2 workers for the same project/account, in a Service Binding fashion. When deployed, the workers A is successfully able to call B. But locally, the Service Binding is actually undefined. Anyone can help? I have no idea why it can't see each other when running locally.
This is my env during dev, for Workers A (caller):
And this is for Workers B (being called):
When I run with --remote (using Wrangler v3.0.0), I get this error: text: 'workers.api.error.service_binding_env_error: could not resolve binding "SERVICES":
environment "dev" not found for service "workers-services" [code: 10144]'
These are however separate project, one is Bundled (A) and one is Unbound (B). One is nodejs compat (B), one is not (A).
So, to summarize:
- when running with
- when running locally (which is the default since wrangler v3.0.0 I assume), the
- running live (after deploy), no problem.
This is my env during dev, for Workers A (caller):
And this is for Workers B (being called):
When I run with --remote (using Wrangler v3.0.0), I get this error: text: 'workers.api.error.service_binding_env_error: could not resolve binding "SERVICES":
environment "dev" not found for service "workers-services" [code: 10144]'
These are however separate project, one is Bundled (A) and one is Unbound (B). One is nodejs compat (B), one is not (A).
So, to summarize:
- when running with
--remote- when running locally (which is the default since wrangler v3.0.0 I assume), the
env.SERVICEundefined- running live (after deploy), no problem.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
