You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bun Shell doesn't find prog, even though it's in the PATH for the Shell context.
Additional information
Note: the example can be more simple. For completeness sake I've included all the steps into a single command line. It seems like any executable file in any location will not be found by Bun Shell if that location was added to the Bun Shell environment PATH variable after bun startup, either locally or globally. (i.e. $`...`.env() or $.env()). Using an absolute path, a non-hidden path or adding the location to the end of PATH doesn't make a difference either. It's almost as if Bun Shell's search path is set upon bun execution and not updated by any calls to .env.
Changing the PATH variable before bun invocation resolves the issue, e.g.
PATH=".mypath:$PATH" bun index.ts
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.0.35
What platform is your computer?
Linux 5.15.146.1-microsoft-standard-WSL2 x86_64 unknown
What steps can reproduce the bug?
Create index.ts
Run it
Try running equivalent from any shell:
What is the expected behavior?
Bun Shell should find and run
prog
What do you see instead?
Bun Shell doesn't find
prog
, even though it's in the PATH for the Shell context.Additional information
Note: the example can be more simple. For completeness sake I've included all the steps into a single command line. It seems like any executable file in any location will not be found by Bun Shell if that location was added to the Bun Shell environment PATH variable after bun startup, either locally or globally. (i.e.
$`...`.env()
or$.env()
). Using an absolute path, a non-hidden path or adding the location to the end of PATH doesn't make a difference either. It's almost as if Bun Shell's search path is set upon bun execution and not updated by any calls to.env
.Changing the PATH variable before bun invocation resolves the issue, e.g.
The text was updated successfully, but these errors were encountered: