Javascript: Console.logs do not appear when using Nodejs.
Discord username (optional)
No response
Describe the bug
Writing a Node CLI tool, and using console.log does not always output, or if it does, it's being hidden. I've tested the same code across Warp and iTerm2 and iTerm2 renders it correctly.
To Reproduce
- Import
inquirerto a Node project. - Create an
inquirerprompt of any type. - When the promise resolves,
console.logthe returned data.
Expected behaviour
A simple console.log message when using console.log.
Screenshots
Operating System
MacOS
OS Version
13.1
Shell Version
zsh 5.8.1 (x86_64-apple-darwin22.0)
Warp Version
v0.2023.02.21.08.03.stable_01
Additional context
In terms of the next question Does this block you from using Warp daily? No, but it certainly makes it a hell of a lot harder to build my app without being able to see what's going on. I still love Warp, though. I love it so very much.
Does this block you from using Warp daily?
No
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
Hi @nrthbound, Thank you for submitting this!
Struggling to reproduce this issue as we don't have any ready examples. Could you please provide a sample repo or files we can use to test, reproduce, and confirm this issue?
Unfortunately, I can't share the repo for this project. But it seems to be
when you're trying to console.log from a promise. It's not a big deal, as
I can build the app with iTerm2 for testing. Just thought it was odd the
exact same code shows the console log in iTerm2 just fine, but not in Warp.
On Mon, Feb 27, 2023 at 1:11 PM Danny Neira @.***> wrote:
Hi @nrthbound https://github.com/nrthbound, Thank you for submitting this!
Struggling to reproduce this issue as we don't have any ready examples. Could you please provide a sample repo or files we can use to test, reproduce, and confirm this issue?
— Reply to this email directly, view it on GitHub https://github.com/warpdotdev/Warp/issues/2711#issuecomment-1446813780, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUQKIX7N6WSIN45HPKJNITWZTU4JANCNFSM6AAAAAAVHV5AYA . You are receiving this because you were mentioned.Message ID: @.***>
Any updates here? I am facing this issue