Chrome Debug Task cannot debug engine code about cocos-engine

[minggo]

What platform did you debug on?

[smallmain]

What platform did you debug on?

MacOS, this problem should not be related to the system.

What I may not have made clear enough is that when debugging a project using VSCode, a single-step breakpoint does not allow access to the engine code because the source diagram path is wrong.

[minggo]

debugging a project using VSCode

It sounds interesting, could i know how you use VSCode to debug engine code?

[smallmain]

Honey, this is a built-in feature of the engine...

i say if the project code has code similar to this.node.setPosition(), then when I enter the function call with a single-step breakpoint, because it is the code of the engine part, an error will be reported and cannot be entered.

So why can debug normally in Chrome DevTools?
After my search, it seems that DevTools has an automatic redirection function, but VSCode does not.
So your sourcemap must be absolutely correct.

[minggo]

Oh, good to know. I don't know and use it.
Thanks.

[smallmain]

Oh, good to know. I don't know and use it. Thanks.

You're welcome, by the way, it would be great if it could support debugging Editor Preview in VSCode. The simplest way would be to expose a debugging port.

Or going one step further, it would be great if you could debug at breakpoints regardless of whether it is in Playing Mode like Unity.

I know that Electron is a multi-process model, which can generally be implemented very simply through the Multi-target debugging function of VSCode. document

[minggo]

Sounds good.