Failed to Detect Deno
See original GitHub issueI’m experiencing the same issue as https://github.com/justjavac/vscode-deno/issues/78; starting a new issue here since this seems to be the location of new development.
Mac Mojave 10.14.6 VS Code 1.45.0 VS Code Deno Extension version 1.27.0 Deno 1.0.0
Environment
$ deno info
DENO_DIR location: "/Users/ME/.deno"
Remote modules cache: "/Users/ME/.deno/deps"
TypeScript compiler cache: "/Users/ME/.deno/gen"
$ deno eval 'console.log(JSON.stringify(Deno.version))'
{"deno":"1.0.0","v8":"8.4.300","typescript":"3.9.2"}
$ env | grep -i deno
DENO_INSTALL=/Users/ME/.deno
DENO_DIR=/Users/ME/.deno
$ which deno
/Users/ME/.deno/bin/deno
I use zsh as my main shell environment.
I tracked the error down to https://github.com/denoland/vscode_deno/blob/9a684b5a735b17b6bedae9a64e68f0223cfe0988/client/src/utils.ts#L64 and saw it’s using execa
. From the execa README.
Unless the shell option is used, no shell interpreter (Bash, cmd.exe, etc.) is used, so shell features such as variables substitution (echo $PATH) are not allowed.
I export DENO_INSTALL
and DENO_DIR
in my .zshrc file and add it to the path. Perhaps execa
isn’t finding Deno because it’s not in the standard PATH locations?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top GitHub Comments
Other people have encountered the same problem, so I should fix this problem
same problem encountered here too.
In case anyone lands here from google, a workaround is adding this to the end of
~/.zshrc
:… at least until the extension is fixed, to detect the executable from
$DENO_INSTALL