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
* feat: add debugger_cmd config
This is to allow providing a command in PATH that launches the debug server,
instead of having to deal with providing absolute paths.
* add unit
Co-authored-by: charburgx <charburgx@gmail.com>
Copy file name to clipboardExpand all lines: lua/dap-vscode-js/init.lua
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
---@classSettings @Plugin configuration options
4
4
---@fieldnode_pathstring: Path of node executable. Defaults to $NODE_PATH, and then "node"
5
5
---@fielddebugger_pathstring: Path to vscode-js-debug. Defaults to (runtimedir)/site/pack/packer/opt/vscode-js-debug
6
+
---@fielddebugger_cmdstring[]?: The command to use to launch the debug server. This option takes precedence over both `node_path` and `debugger_path`.
6
7
---@fieldadaptersstring[]: List of adapters to configure. Options are 'pwa-node', 'pwa-chrome', 'pwa-msedge', 'node-terminal', 'pwa-extensionHost'. Defaults to all. See https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md for configuration options.
0 commit comments