'With webpack / source maps / Chrome devtools, stepping into a function call requires several hops
I'm evaluating webpack for a 10K-line JavaScript app with a bit of PaperScript. To test debugging (in Chrome devtools) I configured a tiny test project with source maps (devtool: 'eval-source-map'), including a simple custom loader to convert the PaperScript to JavaScript.
Setting a breakpoint in a source file works fine. (So impressive!) But when I step into a function imported from another JS file I land in webpack-generated code, and it takes 3 hops to reach my source code.
Certainly not a dealbreaker, but interestingly when I step into a call to a function imported from a PaperScript file (which uses an identity source map generated by my custom loader) I reach my source code in 1 hop.
Do others experience these multiple hops? Is there something I can configure to eliminate them?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|