Starting a couple of weeks ago suddenly both VS Code and Chrome DevTools debuggers are no longer working correctly for my large Deno project. It is impossible to trace the program execution in the source code and inspect variables. Seems that the code is out-of-sync, like if the source maps between js and ts are inconsistent or badly generated. I'm working with Deno since the first stable version, having a smooth and pleasant experience and I've never faced this problem yet.
To diagnose the problem I have: upgraded Deno, uninstalled and downgraded Deno to a previous working version, deleted the local Deno cache, uninstalled and reinstalled VS code, and reinstalled the Deno VS code extension. Then I used another PC (both on win 10), attached Chrome Dev Tools debugger, and changed several launch.json configurations. Even the tests are impossible to trace with the debugger. The step execution jumps randomly across lines and files.
Fortunately, most of my program runs correctly, everything is fine and I can make progress on other areas except the portion that is related to MongoDbAtlas usage that I have to fix with the debugger. Any idea except starting to spread around many console.logs through the code? Has someone faced similar problems recently?
The project uses several Deno std libraries, Drash, Ajv, Three, Mongo, and some others.
The thing is becoming increasingly annoying and I'm wasting a bunch of time. Any help will be very appreciated. Thank you.