Debugging Edge (Chromium) extensions with vscode-edge-debug and sourcemaps

Copper Contributor

Howdy,

 

Before I go and file an issue somewhere, wanted to perform a sanity check here.

 

I’m trying to debug a useful little extension for Chrome. I set up vscode-edge-debug with an Attach configuration, launched the browser with remote debug port, loaded unpacked extension folder, and attach is successful.

 

SourceMap loading, however, appears to be brokey. Snippet from trace log:

 

[18:17:20.690 UTC] ← From target: {"method":"Debugger.scriptParsed","params":{"scriptId":"593","url":"chrome-extension://nkfgmdgpgabmnjikknfhcnnikpmomkil/contentscript.js","startLine":0,"startColumn":0,"endLine":3836,"endColumn":41,"executionContextId":216,"hash":"26a0d10107f9b1fc056a1e7ba7000198243a01ce","executionContextAuxData":{"isDefault":false,"type":"isolated","frameId":"05098280A1A2C801335DCFE6218A1931"},"isLiveEdit":false,"sourceMapURL":"contentscript.js.map","hasSourceURL":false,"isModule":false,"length":131990}}

[18:17:20.690 UTC] SourceMaps.loadSourceMapContents: Could not download sourcemap from chrome-extension://nkfgmdgpgabmnjikknfhcnnikpmomkil/contentscript.js.map

 

But if I paste that chrome-extension:// sourcemap URI into the browser window, it works fine.

 

Version 75.0.140.0 (Official build) canary (64-bit)

Ext: https://github.com/tomitm/lists

Entire log attached.

 

Thoughts?

 

/rafael

1 Reply

@Rafael Rivera 

 

This was great information. If it was still a Chrome extension and not a Microsoft Edge Insider Build Extension at the time, that may be part of the issue. Otherwise, it is likely that the issue is corrected in subsequent updates.

 

Gabriel