vscode_deno: could not find deno in path, please install deno

I hoped for intellisence on deno commands in .ts files and .js files when installing this extension.

I’m on Ubuntu , gnome

Steps to reproduce

i created a docker container
started container
connected vscode to docker container
inside container switched user, added sudo rights
installed deno with curl according the docs.
updated .bashrc for new user with export path 7.reload vscode
deno works in terminal
installed deno vscode extension 10 added .vscode/settings.json to root of project { “deno.enable”: true }
added .ts or .js file to project and tried deno. --> no intellisence, only “Could not find ‘deno in your $PATH’…” at bottom right of screen

**Allready tried **

reinstalling extension
reinstalling deno under root user
changed settings.json to different locations

tnx for any advice or help

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 9
Comments: 26 (5 by maintainers)

Most upvoted comments

I had the same issue. I resolved it with:

sudo ln -s /home/losintikfos/.deno/bin/deno /usr/bin
Restart vscode.

+16

losintikfos on Dec 3, 2020

Same issue, perhaps related to fish shell

Work around for a homebrew installed deno was sudo ln -s /opt/homebrew/bin/deno /usr/local/bin/

tim-field on Feb 6, 2021

Could I request a interim fix being a option to override to a manually entered path to a Deno Executable?

I would add that just in general as a backup as sometimes you may want to run a specific version of Deno as opposed to the global one and a workspace override would allow for that.

jcc10 on Nov 14, 2020

@JSchermers which deno and echo $PATH from the integrated terminal within vscode please…

kitsonk on Oct 11, 2020

Thanks. That worked! Didn’t need to give the flatpak access to that directory since it already has host access.

On Wed, 6 Mar 2024, 07:13 Andrey Dudnik, @.***> wrote:

@andreyddk https://github.com/andreyddk did you find a solution for using deno inside a flatpak VS Code?

Hi! Actually I dont remember exactly, but you cant try install deno via script on official site in $HOME/.deno, next install the Flatseal and set permissions for vscode to file system of $HOME/.deno

— Reply to this email directly, view it on GitHub https://github.com/denoland/vscode_deno/issues/234#issuecomment-1980101105, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJB5FCOYUACYS6WVTCOQ5KDYW2QWXAVCNFSM4R2D66K2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJYGAYTAMJRGA2Q . You are receiving this because you commented.Message ID: @.***>

vixalien on Mar 6, 2024

I still have this issue, installed Deno via Homebrew but the extension can’t seem to find the executable.

I have to manually set deno.path in VS Code settings.json as a workaround.

which deno shows /opt/homebrew/bin which is already in echo $PATH.

I am using oh-my-zsh so I suspect that VS Code gives a different environment to the extension, without loading up the omz plugins? The homebrew PATH comes from ~/.zprofile instead of ~/.zshrc which maybe the clue here.

The contents of my .zprofile has only one line:

eval $(/opt/homebrew/bin/brew shellenv)

vicary on Sep 27, 2022

Note: for me, the workaround is not starting VS Code “normally” (ie. from the /Applications folder or the Launchpad). When I instead navigate to my project directory in the terminal and then start VS Code with code . it works.

teroyks on Feb 1, 2021

I have the same issue on macOS. Screenshot is from the VS Code internal terminal.

teroyks on Feb 1, 2021