Skip to content

windows, after upgrade to 1.3, bun run --bun any-global-pkg would hang in git bash, while powershell works normally #23530

Closed

Description

@cuipengfei

What version of Bun is running?

1.3.0

What platform is your computer?

Windows 11

What steps can reproduce the bug?

bun run --bun cowsay hello

just this command above, if run in git bash, it gets stuck forever, i can see a bun process in windows task manager, but no console output

if the same thing runs in powershell, then it works ok

What is the expected behavior?

git bash should print cowsay as well

as well as other global pkgs

What do you see instead?

git bash no output , hangs

Additional information

No response

Activity

  1. linear commented on Oct 12, 2025

    @linear
  2. added
    windowsAn issue that is known to occur on Windows
    bun installSomething that relates to the npm-compatible client
    and removed on Oct 12, 2025
  3. OysteinAmundsen commented on Oct 13, 2025

    @OysteinAmundsen

    I have the same issue. But running in cmd for windows, with unix tools installed through git for windows. Don't know if that has any connection.

    bun install works, but any other command like bunx create-nx-workspace@latest will hang forever.

    I downgraded to bun v1.2.4, and no longer experience the issue.

  4. Jarred-Sumner commented on Oct 23, 2025

    @Jarred-Sumner
    Collaborator

    Fixed in Bun v1.3.1. This was caused by incorrectly handling non-ASCII environment variables.

    Please upgrade to Bun v1.3.1 to get the fix.

  5. cuipengfei commented on Oct 25, 2025

    @cuipengfei
    Author

    Fixed in Bun v1.3.1. This was caused by incorrectly handling non-ASCII environment variables.

    Please upgrade to Bun v1.3.1 to get the fix.

    thanks, I can confirm it is working well for windows + git bash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingbun installSomething that relates to the npm-compatible clientwindowsAn issue that is known to occur on Windows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions