Closed Niki2k1 closed 9 months ago
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 😅
Environment
Windows 11 23H2 Powershell / CMD Node v20.11.1
Reproduction
I even get this issue when using a minimal setup like this:
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.
But when running the example:
noting.
I would love to get any help trying to debug this.
Additional context
No response
Logs
No response