"Could not read source map ..." #169733
Comments
|
I'm also seen a lot of The weird thing is the errors reference paths on node_modules but my extension is only importing It seems I'm seeing errors related to some internal vscode code, because they appear even if I add |
|
On 1.74.0 I only get: But on 1.74.1 I get: There are 385 lines in total |
connor4312
added
bug
|
I don't know if this is the same bug or not, but I'm using Quasar/Vue building a PWA and for the last few months I've started getting getting hundreds of messages for
If I try using Attached is a |
|
@jaybo in your case, that was a result of microsoft/vscode-js-debug#1410, since the debugger will now look for recursively included sourcemaps. And, as a result of your gets resolved to which are inside the included sourcemap resolution locations, but obviously not valid. You should be able to just remove the {
"type": "chrome",
"request": "launch",
"name": "dzweb Launch Chrome",
"url": "https://localhost:44346"
},I would need trace logs from others to see what's going on there. /jsDebugLogs |
|
Please collect trace logs using the following instructions:
|
|
@connor4312 Removing |
|
I am also encountering the same issue, it seems to be loading sourcemaps for things that are neither deps of my project, nor paths I can find in the VScode.app in my vscode-debugadapter-8a044e9e.json.gz
{
"version": "0.2.0",
"trace": true,
"configurations": [
{
"name": "Extension",
"trace": true,
"type": "extensionHost",
"request": "launch",
"runtimeExecutable": "${execPath}",
"args": [
"--extensionDevelopmentPath=${workspaceFolder}"
],
}
]
}Here is a small sample of the debug console output when i launch the extension using Version: 1.75.1 (Universal) node version |
|
Oh, I see what's happening, thanks. We weren't re-checking |
|
The fix will be in the next nightly build, please try it out and let me know if the fix works for you. |
* fix: recursive source map resolution parsing ignored locations Fixes microsoft/vscode#169733 * fix long-standing test flake
and others
Version: 1.74.2
Commit: e8a3071
Date: 2022-12-20T10:26:09.430Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0
Sandboxed: No
When I try to debug any extension I get the following errors in the Debug Console:
I think this started with vscode 1.74 but I'm not sure.
I also tried to change the launch.json to use "resolveSourceMapLocations"
{ "version": "0.2.0", "configurations": [ { "type": "extensionHost", "request": "launch", "name": "Extension", "preLaunchTask": "npm", "runtimeExecutable": "${execPath}", "args": [ "--extensionDevelopmentPath=${workspaceFolder}" ], "outFiles": [ "${workspaceFolder}/out/**/*.js" ], "smartStep": true, "skipFiles": [ //"inspector_async_hook.js", //"async_hooks.js", "**/extensionHostProcess.js" ], "resolveSourceMapLocations": [ "${workspaceFolder}/**", "!**/node_modules/**" ] } ] }But that does not help either.
I can't change the type to pwa-node as suggested somewhere, because then I cannot debug the extension anymore.
The text was updated successfully, but these errors were encountered: