No console output at all
Niki2k1 opened this issue Β· comments
Environment
Windows 11 23H2
Powershell / CMD
Node v20.11.1
Reproduction
I even get this issue when using a minimal setup like this:
const { consola } = require("consola");
consola.info("Test");
Describe the bug
On my windows machine I have no console output at all. In WSL everything is working fine.
I noticed first when using nuxt. But tried with the minimal consola usage stated in the reproduction.
noting.
I would love to get any help trying to debug this.
Additional context
No response
Logs
No response
can you please share your environment variables in shell?
You could use gci env:* | sort-object name
for PS term
Important
Please make any sensitive ones before pasting
Sure.
Name Value
---- -----
ALLUSERSPROFILE C:\ProgramData
APPDATA C:\Users\βββββββββ\AppData\Roaming
ChocolateyInstall C:\ProgramData\chocolatey
ChocolateyLastPathUpdate 133052981084636025
CommonProgramFiles C:\Program Files\Common Files
CommonProgramFiles(x86) C:\Program Files (x86)\Common Files
CommonProgramW6432 C:\Program Files\Common Files
COMPUTERNAME LAPTOP-βββββββ
ComSpec C:\WINDOWS\system32\cmd.exe
DriverData C:\Windows\System32\Drivers\DriverData
GOPATH C:\Users\βββββββββ\go
HOMEDRIVE C:
HOMEPATH \Users\βββββββββ
LOCALAPPDATA C:\Users\βββββββββ\AppData\Local
LOGONSERVER \\LAPTOP-βββββββββ
NUMBER_OF_PROCESSORS 16
OculusBase C:\Program Files\Oculus\
OneDrive C:\Users\βββββββββ\OneDrive - ββββββββββββββββββ
OneDriveCommercial C:\Users\βββββββββ\OneDrive - ββββββββββββββββββ
OS Windows_NT
Path C:\Program Files\Oculus\Support\oculus-runtime;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\...
PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.CPL
PNPM_HOME C:\Users\βββββββββ\AppData\Local\pnpm
POWERSHELL_DISTRIBUTION_CHA... MSI:Windows 10 Pro
PROCESSOR_ARCHITECTURE AMD64
PROCESSOR_IDENTIFIER AMD64 Family 23 Model 104 Stepping 1, AuthenticAMD
PROCESSOR_LEVEL 23
PROCESSOR_REVISION 6801
ProgramData C:\ProgramData
ProgramFiles C:\Program Files
ProgramFiles(x86) C:\Program Files (x86)
ProgramW6432 C:\Program Files
PSModulePath C:\Users\βββββββββ\Documents\WindowsPowerShell\Modules;C:\Program Files\WindowsPowerShell\Modul...
PUBLIC C:\Users\Public
PYTHON C:\Users\βββββββββ\AppData\Local\Programs\Python\Python39
SESSIONNAME Console
SystemDrive C:
SystemRoot C:\WINDOWS
TEMP C:\Users\βββββββββ\AppData\Local\Temp
TEST something
TMP C:\Users\βββββββββ\AppData\Local\Temp
USERDOMAIN AzureAD
USERDOMAIN_ROAMINGPROFILE AzureAD
USERNAME βββββββββ
USERPROFILE C:\Users\βββββββββ
windir C:\WINDOWS
WSLENV WT_SESSION:WT_PROFILE_ID:
WT_PROFILE_ID ββββββββββββββββββ
WT_SESSION ββββββββββββββββββ
Full PATH:
C:\Users\βββββββββ\AppData\Local\Programs\Python\Launcher\;%PNPM_HOME%;C:\Users\βββββββββ\AppData\Local\pnpm;C:\Users\βββββββββ\AppData\Local\Microsoft\WindowsApps;C:\Users\βββββββββ\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\βββββββββ\AppData\Roaming\nvm;C:\Users\βββββββββ\.dotnet\tools;C:\Users\βββββββββ\.deno\bin;C:\Users\βββββββββ\AppData\Local\Microsoft\WindowsApps;C:\Users\βββββββββ\go\bin;C:\Users\βββββββββ\AppData\Roaming\nvm;C:\Program Files\stripe-cli;C:\Users\βββββββββ\.bun\bin;;%USERPROFILE%\go\bin;C:\Users\βββββββββ\AppData\Roaming\npm
TEST something
This might be the devil. TEST
is detecting a test runner env and causes to limit to warn+ log levels.
Oh wow, thank you very much. Removing that Environment Variable works. I would've never found it myself. I probably used the TEST env for ... testing somewhen else π