Support "node", "chrome", "msedge", "extensionHost" debugTypes.
#68
Comments
80avin
changed the title
"node", "chrome", "msedge", "extensionHost" debugTypes."node", "chrome", "msedge", "extensionHost" debugTypes.
80avin
added a commit
to 80avin/LazyVim
that referenced
this issue
Apr 14, 2024
… "pwa-node" "pwa-node" is deprecated in [vscode-js-debug](https://github.com/microsoft/vscode-js-debug) as documented in issue mxsdev/nvim-dap-vscode-js#68
80avin
added a commit
to 80avin/LazyVim
that referenced
this issue
May 1, 2024
… "pwa-node" "pwa-node" is deprecated in [vscode-js-debug](https://github.com/microsoft/vscode-js-debug) as documented in issue mxsdev/nvim-dap-vscode-js#68
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As can be seen in vscode-js-debug/src/common/contributionUtils.ts, the
"pwa-*"debug types are not preferred.Also, as seen in https://github.com/microsoft/vscode-js-debug/blob/2152210dc7c3933e2b4ef7c72d72cf2fef765760/src/build/generate-contributions.ts#L1090-L1098 , vscode will generate a warning if non preferred debug types are used.
Hence, I suggest we add the debug types
"node", "chrome", "msedge", "extensionHost"in addition to"pwa-*"versions of these.This also creates issues when we are importing the autogenerated
.vscode/launch.jsonfile which doesn't havepwa-prefix.The text was updated successfully, but these errors were encountered: