Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Console Ninja breaks debug console #296

Open
Danny220 opened this issue Apr 29, 2024 · 3 comments
Open

[Bug]: Console Ninja breaks debug console #296

Danny220 opened this issue Apr 29, 2024 · 3 comments

Comments

@Danny220
Copy link

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

image

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
    image
  3. open devtools on chrome and trigger the debugger

Log output

i could not find that folder
@ArtemGovorov
Copy link
Member

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

ng

Also works as expected in a simple button click handler:
Screenshot 2024-04-30 at 9 25 14 AM

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
Copy link
Author

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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants