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
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.0. Please try upgrading to the latest version and checking whether this issue remains.
Fixesmicrosoft/vscode#200665
Requires use of my picomatch fork due to micromatch/picomatch#125.
We could alternatively use brace expansion until that's fixed, but that's much less
efficient that using a logical or.
connor4312
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Dec 13, 2023
Thanks for the nice issue, you can also work around this by manually specifying the outFiles in your launch.json to include .{js,mjs,cjs} instead of just .js
Fixesmicrosoft/vscode#200665
Requires use of my picomatch fork due to micromatch/picomatch#125.
We could alternatively use brace expansion until that's fixed, but that's much less
efficient that using a logical or.
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
pnpm init
tsup.config.ts
.vscode/launch.json
pnpm build
Run and Debug
, testDebug js
andDebug
Files with the ".mjs" suffix cannot be debugged, but files with the ".js" suffix can be debugged.
add
"type":"modules"
topackage.json
, and runpnpm build
. Files with the "*.cjs" suffix cannot be debugged, the same problem as ".mjs"The full demo is https://github.com/my-alpha/vscode-debug-esm-cjs
The text was updated successfully, but these errors were encountered: