-
Notifications
You must be signed in to change notification settings - Fork 23
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 is waiting for runtime events #277
Comments
The log that you provided looks like it's for node 14:
Can you please provide the full trace.log content for your project using both Node 14 (where it's working) and node 18 where it's not working? To minimize the content of the trace, you may delete the |
This is the trace log using node 18. Am I doing something wrong? I deleted trace.log and node 14 to generate this full trace.log. (I'm using nvm btw)
|
It looks like you have not provided us with the full trace.log content. We're expecting to see additional entries that will help use understand what Console Ninja is doing on your system, such as:
Can you please provide us with the full trace contents when you use node 14 and log something successfully, and also the full trace file when you use node 18 and attempt to log something and it does not work for you? Please take the following steps:
If you have concerns about sharing the content in your trace.log publicly, you may email us: [email protected]. |
Oh sorry okay. This is both full trace.log Using node v14
Using node v18
|
Both We've discovered a bug when using From your log file, it looks like Console Ninja is operating correctly but the code with the log files is not actually executing. Can you please tell us the exact steps you're taking and provide some screenshots of where you are using If possible, can you please provide a sample repo along with step-by-step instructions to reproduce your problem? If the screenshots don't help, we will definitely need this information. |
What happened?
I was expecting to print console.log() in vscode but it doesn't work. I noticed that I'm getting this output in trace.log. Currently I'm working with nvm using node 18
Version
v1.0.294
Steps to reproduce (or sample repo)
Not sure. I've been using the same repo with nvm node 14 and it works fine
Log output
The text was updated successfully, but these errors were encountered: