Breakpoints not set properly when running with vitest

[louislatreille-cb]

Breakpoints not set properly when running with vitest

[louislatreille-cb]

Update:

I've noticed the following:

• Breakpoints in the log file being executed are bound properly and immediately.
• Breakpoints in the API packages are eventually bound, when the debugger is fully started
• Breakpoints in the common package are never bound, and even after the debugger is fully started, it's impossible to set any in the common package
• Stepping into code from the common package shows incorrect lines/files

Sent another log file when going through the steps that lead to the above conclusions.

[connor4312]

This is a common issue in monorepos, you're building your "common" code, but then your tooling is not "following" the sourcemaps in the compiled code. When it's bundling the code, it's creating sourcemaps that reference the already compiled bundle rather than your actual source code, e.g.

{
	"version": 3,
	"sources": [
		"chunk-ZZYPPKAZ.js" // <- should be your actual sources, not just the chunk
	],

I think that you might not be building with sourcemaps in your common code, as both vitest/esbuild and js-debug have logic that may handle this case if that were so.

[louislatreille-cb]

@connor4312 Thanks for the reply.

Actually, we do generate source maps for our common package. In fact, everything was working fine not too long ago. I tried going as far as 3 months back into our commit history, but still have the same issues with the debugger, which leads me to believe that we're either doing something wrong with our launch configs, or something changed with the debugger.

Based on your comment, I tried disabling code splitting in our bundler. This eliminates all the chunk files. Still getting the exact same issue though. Sent another log file to your email with that.

Here's another look into my issues:

This is the result after clicking twice on line 308 in calculateUtilities.ts. As you can see, the breakpoints make no sense.