Bug: taze -w in vscode extension

[Simon-He95]

Describe the bug

Reproduction

in vscode extension use npx taze -w

System Info

System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 3.85 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - ~/.local/state/fnm_multishells/77490_1737124605009/bin/node
    Yarn: 1.22.22 - ~/.local/state/fnm_multishells/77490_1737124605009/bin/yarn
    npm: 10.8.1 - ~/.local/state/fnm_multishells/77490_1737124605009/bin/npm
    pnpm: 9.6.0 - ~/.local/state/fnm_multishells/77490_1737124605009/bin/pnpm
    bun: 1.1.21 - ~/.bun/bin/bun
    Watchman: 2024.09.09.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 131.0.6778.266
    Safari: 17.5

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)