Skip to content

Commit f7e45ba

Browse files
Adds changelog for remote bindings beta (#23105)
* adds changelog for remote bindings beta * adds changelog for remote bindings beta * small edits to copy * Update src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx Co-authored-by: Brendan Irvine-Broque <[email protected]> * Update src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx Co-authored-by: Brendan Irvine-Broque <[email protected]> * Update src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx Co-authored-by: Brendan Irvine-Broque <[email protected]> * Update src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx Co-authored-by: Brendan Irvine-Broque <[email protected]> --------- Co-authored-by: Brendan Irvine-Broque <[email protected]>
1 parent 884a07e commit f7e45ba

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Remote bindings public beta - Connect to remote resources (D1, KV, R2, etc.) during local development
3+
description: You can now connect to R2 buckets, D1 databases, and other resources running on Cloudflare, while running your Worker's code locally, on your own machine.
4+
products:
5+
- workers
6+
date: 2025-06-18T17:00:00Z
7+
---
8+
9+
import { WranglerConfig, Aside } from "~/components";
10+
11+
Today [we announced the public beta](https://github.com/cloudflare/workers-sdk/discussions/9660) of [remote bindings](/workers/development-testing/#remote-bindings) for local development. With remote bindings, you can now connect to deployed resources like [R2 buckets](/r2/) and [D1 databases](/d1/) while running Worker code on your local machine. This means you can test your local code changes against real data and services, without the overhead of deploying for each iteration.
12+
13+
## Example configuration
14+
15+
To enable remote mode, add `"experimental_remote" : true` to each binding that you want to rely on a remote resource running on Cloudflare:
16+
17+
<WranglerConfig>
18+
19+
```jsonc title="wrangler.jsonc"
20+
{
21+
"name": "my-worker",
22+
"compatibility_date": "$today",
23+
24+
"r2_buckets": [
25+
{
26+
"bucket_name": "screenshots-bucket",
27+
"binding": "screenshots_bucket",
28+
"experimental_remote": true,
29+
},
30+
],
31+
}
32+
```
33+
34+
</WranglerConfig>
35+
36+
When remote bindings are configured, your Worker **still executes locally**, but all binding calls are proxied to the deployed resource that runs on Cloudflare's network.
37+
38+
**You can try out remote bindings for local development today with:**
39+
40+
- [Wrangler v4.20.3](/workers/development-testing/#using-wrangler-with-remote-bindings): Use the `wrangler dev --x-remote-bindings command`.
41+
- The [Cloudflare Vite Plugin](/workers/development-testing/#using-vite-with-remote-bindings): Refer to the documentation for how to enable in your Vite config.
42+
- The [Cloudflare Vitest Plugin](/workers/development-testing/#using-vitest-with-remote-bindings): Refer to the documentation for how to enable in your Vitest config.
43+
44+
**Have feedback?**
45+
Join the discussion in our [beta announcement](https://github.com/cloudflare/workers-sdk/discussions/9660) to share feedback or report any issues.

0 commit comments

Comments
 (0)