Clicking on console log origin links in the developer console opens the transpiled source despite having an inline source map
Reported by
john.dav...@gmail.com,
Aug 12
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
Steps to reproduce the problem:
1. console.log("hi") from a file that is to be transpiled with an inline source map
2. run the file with the chrome inspector
3. click on the origin link
What is the expected behavior?
It should load the pretty source of the original file and not the transpiled ugly code.
What went wrong?
It opens the wrong file.
Did this work before? N/A
Chrome version: 68.0.3440.106 Channel: stable
OS Version: OS X 10.13.5
Flash Version:
,
Aug 13
It sounds like I fixed it for ndb but broken for DevTools.. I will take a look.
,
Oct 4
I checked current Chrome Stable, latest Google Chrome Canary and ndb. It works that everything works as expected with esm and sourceMap: true flag.
,
Oct 4
Thank you kozy! |
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 12