I'm hoping this is a tip that may help someone with debugging javascript more easily when using Chrome/Edge dev tools.
I noticed the dev wiki promotes using debugger; statements in javascript which requires making a code change to set a breakpoint. I'm assuming this is because refreshing via F5 tends to remove breakpoints due to some cache buster values that are added to the downloaded javascript filename. However, I found that adding the following line to the end of the javascript file helps resolve the issue by creating the proper source mapping.
I updated the wiki to reflect this:
https://en.doc.boardgamearena.com/Pract ... yjsfile.js
I noticed the dev wiki promotes using debugger; statements in javascript which requires making a code change to set a breakpoint. I'm assuming this is because refreshing via F5 tends to remove breakpoints due to some cache buster values that are added to the downloaded javascript filename. However, I found that adding the following line to the end of the javascript file helps resolve the issue by creating the proper source mapping.
Code: Select all
//# sourceURL=myfile.js
https://en.doc.boardgamearena.com/Pract ... yjsfile.js