4 ms·
I do because chrome debugger doesn't recognize that because I'm using. Bundler, I don't care about the mess of layers between my code and my errors. Everytime
by cyanydeez 4y ago
I do because chrome debugger doesn't recognize that because I'm using. Bundler, I don't care about the mess of layers between my code and my errors.
Everytime I try to step through, there's all these arbitrary access layers that have to be hit.
- jraph 4y agoTry configuring your bundler so it outputs source maps, and disable js transformations aimed at compatibility with old browsers. Like whatever they do with for..of loops and async/await that makes the code unintelligible. For this, put whatever is needed in the configuration of the bundler to target the latest version of Chrome or Firefox (for instance [1] for babel / webpack). It's worth it really. And maybe in the future bundlers will not be needed anymore. On recent browsers with HTTP2 and gzip compression, I question the need of bundling at all, especially if the dependency tree is limited (yes, that's a HUGE if). With HTTP2 multiplexing / connections kept alive, Good old <script> tags might work quite well now (with type="module"). [1] https://webpack.js.org/loaders/babel-loader/#customize-config-based-on-webpack-target https://webpack.js.org/loaders/babel-loader/#customize-confi...
- hoten 4y agoSounds like you want this? https://dilshankelsen.com/ignore-library-code-while-debugging-browser/#:~:text=If%20you%20know%20upfront%20which,browser%20like%20Vivaldi%20or%20Edge https://dilshankelsen.com/ignore-library-code-while-debuggin....