[Bug]: Console Ninja breaks debug console

[Danny220]

What happened?

I was expecting to debug my angular application in chrome normally, but the only source showen was a random file containing "globalThis._console_ninja" that prevented me to view the original source

Version

1.0.316

CLI command to start your dev tool

nx run-many --target=serve --configuration=local

Steps to reproduce (or sample repo)

1. start up ng serve
2. put debugger
   
3. open devtools on chrome and trigger the debugger

Log output

i could not find that folder

[ArtemGovorov]

@Danny220 We have tried to reproduce the issue, but it's working for us as expected in the latest NG generated app:

Also works as expected in a simple button click handler:

Can you please share a sample repo where the issue can be reproduced?

You can also try to restart Ninja to see if it helps. As a workaround, you may also just pause Ninja (with VS Code Ninja Pause command) prior to debugging.

[Danny220]

It's very confusing for me too, because it's not happening everytime, but pretty often. Unfortunately I can not share a sample repo as the project where it happens is of my job's and it's not open source.
The component where I encountered the issue is very large, could this be a cause?

[ArtemGovorov]

The component where I encountered the issue is very large, could this be a cause?

We have tried nx specifically, also larger components, but still can't reproduce the issue.
Can you please copy and paste your log output from the ~/.console-ninja/trace.log file in your user home directory? The log file can also be opened from hovering the Ninja status bar item in VS Code, and locating the Show Log link in the hover popup.

[Danny220]

I'm very sorry for the late response. Here you go

trace.log

[smcenlly]

Thanks for providing the trace log. Unfortunately it doesn't provide any information to help identify why it's not working for you.

I understand that you can't share your current project, but we will require a sample project to investigate further. We'd suggest taking your public dependency and configuration from your current project and see if you can reproduce the problem in a new code base. I expect you would be able to reproduce the problem if you take this approach.