-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolveCommand
does not always resolve correctly (error in deno_which
)
#133
Comments
resolveCommand
does not always resolve correctlyresolveCommand
does not always resolve correctly (failure in deno_which
)
resolveCommand
does not always resolve correctly (failure in deno_which
)resolveCommand
does not always resolve correctly (error in deno_which
)
Do you see the directory in |
The directory does appear. The extension is
After inspecting the
If I add the symlinked path directly to |
Thanks for investigating! Yeah it appears deno_which needs to handle symlinks. |
Looks like updating Updated
The Deno docs state that
Is this a bug in |
`Deno.stat` throws an error on Windows if the path is a symlink. See dsherret/dax#133.
I investigated and opened denoland/deno#18598 This is not a deno_which issue. |
It appears that
resolveCommand
fails to correctly resolve the location of commands that are available on the system path. This causes scripts to fail with the error thrown here.The following simple example will crash:
The issue lies in deno_which.
Here is a failing test case for
deno_which
:The text was updated successfully, but these errors were encountered: