You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[vite-plugin] improve inspector port handling (#8680)
* [vite-plugin] fix: make sure that the plugin keeps looking for available inspector ports by default
* [vite-plugin] fix: make sure that users can use inspector port `0` to use a random port
* Update packages/vite-plugin-cloudflare/README.md
Co-authored-by: James Opstad <[email protected]>
* move `resolvedInspectorPort` inside `cloudflare` function
* resolve inspector port in configure server
* remove global `resolvedInspectorPort` variable
* Revert "remove global `resolvedInspectorPort` variable"
This reverts commit 8382228.
* remove global `resolvedInspectorPort` variable (and resolve inspector port id in debug middleware)
* improve code and warn when 9229 is not available
* remove unused imports
* remove useless line of code
* Update packages/vite-plugin-cloudflare/src/index.ts
Co-authored-by: James Opstad <[email protected]>
---------
Co-authored-by: James Opstad <[email protected]>
Copy file name to clipboardExpand all lines: packages/vite-plugin-cloudflare/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,7 +376,7 @@ It accepts an optional `PluginConfig` parameter.
376
376
377
377
-`inspectorPort?: number | false`
378
378
379
-
Optional inspector port to use for debugging your workers, for more details on debugging see the [devtools section](#devtools). Can be set to `false`to disable the debugging inspector altogether. Defaults to`9229`.
379
+
Optional inspector port to use for debugging your workers, for more details on debugging see the [devtools section](#devtools). By default the vite plugin will attempt to use the first available port it can find starting at`9229`.
380
380
381
381
> [!NOTE]
382
382
> When running `wrangler deploy`, only your main (entry) Worker will be deployed.
0 commit comments