Could not load source map when I enable debug.javascript.usePreview
See original GitHub issueDescribe the bug
Could not load source map when I enable debug.javascript.usePreview
, if I disable, all work
To Reproduce
I use this project to debug https://github.com/easy-mock/easy-mock
This is my config:
{
"version": "0.2.0",
"configurations": [
{
"name": "Attach",
"port": 9229,
"request": "attach",
"skipFiles": [
"<node_internals>/**"
],
"type": "pwa-node",
"restart": true
},
]
}
Log File
VS Code Version: 1.51.0-insider
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error message "DevTools failed to load SourceMap: Could not ...
Go to the developer tools (F12 in the browser), then select the three dots in the upper right corner, and go to Settings....
Read more >https://raw.githubusercontent.com/Microsoft/vscode...
usePreview ` the default ## 4.12.6 * Respect the `debug.javascript. ... true` in your launch config, but can set it to false to...
Read more >Debugging tools | Playwright 中文文档
Playwright scripts work with existing debugging tools, like Node.js debuggers. ... Defaults; Debugging Selectors; Evaluate Source Maps. Verbose API logs ...
Read more >April 2020 (version 1.45) - Visual Studio Code
When debug.javascript.usePreview is turned on, VS Code's Auto Attach will use a new method provided by js-debug that allows all terminals to work...
Read more >VS Code Previews JavaScript Debugger, Search Editor ...
Developers can try it out by enabling the debug.javascript.usePreview setting in a launch configuration and can report any issues in the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good to hear. I will go ahead and close this, then – the setting is a known quirk with Node 8.
Most likely something is being loaded, possible from your dependencies., that has a comment like
//# sourceURL=server-bundle.js
(which overwrites its path when loaded from V8 loads it, thus preventing us from seeing it’s from node_modules and omitting the warning) and a sourceMapUrl which doesn’t exist.Thank you so much