Chrome Source Mapped Stack Debugging about node-source-map-support

[evanw]

Yes, that is annoying. It seems to depend on whether the code originated from the page or from the console. To be specific, this CoffeeScript code reproduces your issue:

(require '../source-map-support').install()

window.foo = ->
  try
    throw new Error 'foo'
  catch e
    console.log e.stack

foo()

However, calling foo() from the dev console generates a link that looks exactly the same but that takes you to the sources tab instead of initiating a download. Using the web inspector on itself shows that the download link has target="_blank" but the sources tab link doesn't. It looks like it has to do with isExternal in WebInspector.linkifyURLAsNode. You should log a bug with Chrome DevTools to have this fixed.

[olegbl]

Thanks for the prompt response!
I logged a Chromium bug for this issue at https://code.google.com/p/chromium/issues/detail?id=273113

[olegbl]

It looks like this is fixed with the latest Chrome build (or perhaps a few versions ago) despite the Chromium bug still being open.

[evanw]

Weird. It still doesn't seem fixed for me, even on Canary (Version 37.0.2008.2 from today). For me it's actually worse than a new tab. I'm using the "servedir" node package to serve the files, which triggers a download of the *.coffee file.

[olegbl]

Hm, well, I did change the sourcemaps to include the original files within the sourcemaps themselves (the sourcesContent field) - so maybe that's what caused the "fix" for me. Not sure.