Skip to content

Commit 22d8fde

Browse files
correct incorrect instructions
1 parent a5e702a commit 22d8fde

File tree

1 file changed

+2
-9
lines changed
  • src/content/docs/workers/development-testing

1 file changed

+2
-9
lines changed

src/content/docs/workers/development-testing/index.mdx

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -331,16 +331,9 @@ There are two main approaches for this:
331331

332332
- **Remote Durable Objects with local Workers:**
333333

334-
You can run Durable Objects remotely from a Worker using [`wrangler dev --remote`](/workers/wrangler/commands/#dev) and have them interact with local Workers
335-
running on your machine by leveraging Wrangler's [Multiple dev commands](./multi-workers/#multiple-dev-commands) feature.
334+
Although remote bindings for Durable Objects are not currently supported, you can still interact with remote Durable Objects during local development by using remote service bindings.
336335

337-
To do this:
338-
339-
- Start your remote Worker (which contains the Durable Object) using `wrangler dev --remote`.
340-
341-
- In your local Workers' configuration, set the Durable Object's [`script_name`](/workers/wrangler/configuration/#durable-objects) to the name of the remote Worker.
342-
343-
- Run your local Workers with `wrangler dev` to connect to the remote Durable Object.
336+
To do this, deploy a Worker that has a binding to the target Durable Object. Then, configure a remote service binding in your local Worker to point to this deployed Worker. Your local Worker will be able to interact with the Durable Object via the remote service binding, effectively using the deployed Worker as a proxy interface to the Durable Object during local development.
344337

345338

346339
### Important Considerations

0 commit comments

Comments
 (0)