update the experimental_maybeStartOrUpdateRemoteProxySession parameters

Author: dario-piotrowicz

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

@@ -247,7 +247,7 @@ To verify that the certificate exchange and validation process work as expected.
 
 }
 
-```
+````
 </WranglerConfig>
 
 #### [Images](/workers/wrangler/configuration/#images):
@@ -262,7 +262,7 @@ To connect to a high-fidelity version of the Images API, and verify that all tra
 		"experimental_remote": true
   }
 }
-```
+````
 
 </WranglerConfig>
 
@@ -371,7 +371,9 @@ the bindings in an `Unstable_Config` object into a structure that can be passed
 
 This wrapper simplifies proxy session management. It takes:
 
-- The path to your Wrangler config, or an object with remote bindings.
+- An object that either contains
+  - the path to a Wrangler config and the potential environment to targeted
+  - the name of the Worker and the bindings it is using.
 - The current proxy session details (this parameter can be set to `null` or not being provided if none).
 
 It returns an object with the proxy session details if started or updated, or `null` if no proxy session is needed.
@@ -398,34 +400,35 @@ let mf: Miniflare | null;
 let remoteProxySessionDetails: Awaited<ReturnType<typeof experimental_maybeStartOrUpdateRemoteProxySession>> | null = null;
 
 async function startOrUpdateDevSession() {
-	remoteProxySessionDetails = await experimental_maybeStartOrUpdateRemoteProxySession({
-			bindings: {
-				MY_KV: {
-					type: 'kv_namespace',
-					id: 'kv-id',
-					experimental_remote: true,
-				}
-			}
-		},
-		remoteProxySessionDetails
-	);
-
-	const miniflareOptions: MiniflareOptions = {
-		scriptPath: "./worker.js",
-		kvNamespaces: {
-			MY_KV: {
-				id: "kv-id",
-				remoteProxyConnectionString:
-				remoteProxySessionDetails?.session.remoteProxyConnectionString,
-			},
-		},
-	};
+remoteProxySessionDetails = await experimental_maybeStartOrUpdateRemoteProxySession({
+bindings: {
+MY_KV: {
+type: 'kv_namespace',
+id: 'kv-id',
+experimental_remote: true,
+}
+}
+},
+remoteProxySessionDetails
+);
+
+    const miniflareOptions: MiniflareOptions = {
+    	scriptPath: "./worker.js",
+    	kvNamespaces: {
+    		MY_KV: {
+    			id: "kv-id",
+    			remoteProxyConnectionString:
+    			remoteProxySessionDetails?.session.remoteProxyConnectionString,
+    		},
+    	},
+    };
+
+    if (!mf) {
+    	mf = new Miniflare(miniflareOptions);
+    } else {
+    	mf.setOptions(miniflareOptions);
+    }
 
-	if (!mf) {
-		mf = new Miniflare(miniflareOptions);
-	} else {
-		mf.setOptions(miniflareOptions);
-	}
 }
 
 // ... tool logic that invokes `startOrUpdateDevSession()` ...
@@ -460,3 +463,4 @@ When using remote development, all bindings automatically connect to their remot
 
 - When you run a remote development session using the `--remote` flag, a limit of 50 [routes](/workers/configuration/routing/routes/) per zone is enforced. Learn more in[ Workers platform limits](/workers/platform/limits/#number-of-routes-per-zone-when-using-wrangler-dev---remote).
 
+```