From Discord: Built-in --log-level option causes argument parsing issues on Windows due to path splitting

[effect-bot]

Summary

A user reported that using the built-in --log-level option on their CLI breaks access to parent options in subcommands, specifically when running on Windows. The issue arises because the executable path string containing spaces (e.g., 'C:\Program Files\nodejs\node.exe') is split incorrectly using a whitespace delimiter, which causes subsequent argument parsing to shift and fail. This manifests as the parser failing to find expected options such as '--config'. The maintainers acknowledge this as a Windows-specific bug related to path parsing and are considering solutions, with a temporary issue opened for tracking.

Discord thread

https://discord.com/channels/795981131316985866/1443920112259432572