From f20204db07af675d74ad1c0e774d6ebcfeec75ca Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Tue, 4 Nov 2025 01:16:07 +0000 Subject: [PATCH 1/6] Add `--local` flag to `wrangler dev` documentation --- src/content/docs/workers/wrangler/commands.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx index 0e3826b2462046f..0e5dd794c33802b 100644 --- a/src/content/docs/workers/wrangler/commands.mdx +++ b/src/content/docs/workers/wrangler/commands.mdx @@ -246,6 +246,8 @@ None of the options for this command are required. Many of these options can be - Show the interactive dev session. - `--alias` `Array` - Specify modules to alias using [module aliasing](/workers/wrangler/configuration/#module-aliasing). +- `--local` + - Develop against all local resources, this includes both the worker's logic and [remote bindings](/workers/development-testing/#remote-bindings) which will be disabled (behaving exactly as if there were configured with `remote: false`). From d07738937b8df75626a5ca862e61e653056191b1 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Tue, 4 Nov 2025 10:18:51 +0000 Subject: [PATCH 2/6] add `localBindingsOnly` option to `getPlatformProxy` documentation (and remove outdated remote bindings option) --- src/content/docs/workers/wrangler/api.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx index b62b08302b19459..e0d289051265daf 100644 --- a/src/content/docs/workers/wrangler/api.mdx +++ b/src/content/docs/workers/wrangler/api.mdx @@ -300,11 +300,9 @@ const platform = await getPlatformProxy(options); **Note:** If you use `wrangler`'s `--persist-to` option, note that this option adds a subdirectory called `v3` under the hood while `getPlatformProxy`'s `persist` does not. For example, if you run `wrangler dev --persist-to ./my-directory`, to reuse the same location using `getPlatformProxy`, you will have to specify: `persist: { path: "./my-directory/v3" }`. - - `experimental` `{ remoteBindings: boolean }` + - `localBindingsOnly` boolean - Object used to enable experimental features, no guarantees are made to the stability of this API, use at your own risk. - - - `remoteBindings` Enables `getPlatformProxy` to connect to [remote bindings](/workers/development-testing/#remote-bindings). + When set to `true` disables the remote aspect of [remote bindings](/workers/development-testing/#remote-bindings), in the exact same way as if their `remote` configuration was set to `false`. Defaults to `false`. ### Return Type From 29b580fe89f5e40e95ae6fb04b13821797fa81a1 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Tue, 4 Nov 2025 13:30:21 +0000 Subject: [PATCH 3/6] rename `localBindingsOnly` to `remoteBindings` --- src/content/docs/workers/wrangler/api.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx index e0d289051265daf..3f04dac5828485a 100644 --- a/src/content/docs/workers/wrangler/api.mdx +++ b/src/content/docs/workers/wrangler/api.mdx @@ -300,9 +300,9 @@ const platform = await getPlatformProxy(options); **Note:** If you use `wrangler`'s `--persist-to` option, note that this option adds a subdirectory called `v3` under the hood while `getPlatformProxy`'s `persist` does not. For example, if you run `wrangler dev --persist-to ./my-directory`, to reuse the same location using `getPlatformProxy`, you will have to specify: `persist: { path: "./my-directory/v3" }`. - - `localBindingsOnly` boolean + - `remoteBindings` boolean - When set to `true` disables the remote aspect of [remote bindings](/workers/development-testing/#remote-bindings), in the exact same way as if their `remote` configuration was set to `false`. Defaults to `false`. + Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled. ### Return Type From a186902c52e6d2fb0a82241ef3f27f36ca25bf16 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Tue, 4 Nov 2025 16:59:56 +0000 Subject: [PATCH 4/6] add `remoteBindings` option to vite-plugin documentation --- src/content/docs/workers/vite-plugin/reference/api.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/content/docs/workers/vite-plugin/reference/api.mdx b/src/content/docs/workers/vite-plugin/reference/api.mdx index cde4a5e711903eb..6ac27e3938c63ab 100644 --- a/src/content/docs/workers/vite-plugin/reference/api.mdx +++ b/src/content/docs/workers/vite-plugin/reference/api.mdx @@ -73,6 +73,11 @@ It accepts an optional `PluginConfig` parameter. You can inspect the `dist` directory and then run `wrangler deploy -c dist//wrangler.json` for each. ::: +- `remoteBindings` + + Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled, they are by default. + + ## `interface AuxiliaryWorkerConfig` - `configPath` From 87ffd355cb42aee70329185da89128eb0964e432 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Mon, 10 Nov 2025 12:07:32 +0000 Subject: [PATCH 5/6] Update src/content/docs/workers/wrangler/commands.mdx Co-authored-by: Pete Bacon Darwin --- src/content/docs/workers/wrangler/commands.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx index 0e5dd794c33802b..562578d98641acb 100644 --- a/src/content/docs/workers/wrangler/commands.mdx +++ b/src/content/docs/workers/wrangler/commands.mdx @@ -247,7 +247,9 @@ None of the options for this command are required. Many of these options can be - `--alias` `Array` - Specify modules to alias using [module aliasing](/workers/wrangler/configuration/#module-aliasing). - `--local` - - Develop against all local resources, this includes both the worker's logic and [remote bindings](/workers/development-testing/#remote-bindings) which will be disabled (behaving exactly as if there were configured with `remote: false`). + - Run in local mode. In this mode: + - the Worker code is running locally on your machine + - all [remote bindings](/workers/development-testing/#remote-bindings) are disabled, which behaves exactly as if there were configured with `remote: false`. From dffa4dd79de692dcfe05a3994d76f4a72daf7fd9 Mon Sep 17 00:00:00 2001 From: Dario Piotrowicz Date: Mon, 10 Nov 2025 12:21:20 +0000 Subject: [PATCH 6/6] Update src/content/docs/workers/vite-plugin/reference/api.mdx Co-authored-by: Matt Kane --- src/content/docs/workers/vite-plugin/reference/api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/vite-plugin/reference/api.mdx b/src/content/docs/workers/vite-plugin/reference/api.mdx index 6ac27e3938c63ab..c267f5da30decc4 100644 --- a/src/content/docs/workers/vite-plugin/reference/api.mdx +++ b/src/content/docs/workers/vite-plugin/reference/api.mdx @@ -75,7 +75,7 @@ It accepts an optional `PluginConfig` parameter. - `remoteBindings` - Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled, they are by default. + Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled. Defaults to `true`. ## `interface AuxiliaryWorkerConfig`