search

mxsdev / nvim-dap-vscode-js

nvim-dap adapter for vscode-js-debug
276 stars 30 forks source link

Change of entrypoint when installed using Mason #57

Open ungrim97 opened 1 year ago

ungrim97 commented 1 year ago

Newer versions of the vscode-js-debug seem to have alternate builds.

Mason uses the dapDebugServer build rather than the older vsDebugServer. This means that for versions after 1.76.1 of vscode-js-debug there is no '/out/src/vsDebugServer.js', instead the path is Entrypoint path is now js-debug/src/dapDebugServer.js

I suspect the easiest thing will be to update to allow a configurable entry point relative to the debugger_path.

For now those using mason-dap-nvim to install vscode-js-debug can use version 1.76.1 instead of the latest 1.82

ungrim97 commented 1 year ago

Related to #31

ungrim97 commented 1 year ago

Looking further, I think that all of this is as a result of M$ implementing a pure js DAP version of the vscode-js-debug rather than just a VSCode specific implementation that isn't dap compliant.

I am not sure what if anything that changes things for nvim-dap-vscode-js?