Use a task to check if func cli is installed instead of child process

[aaronpowell]

I run WSL2 for my dev and I've been unable to get the launch task to work when running under VS Code Remote WSL, it always tells me that I don't have the core tools installed (hitting this message).

It would appear that this function is returning false, and thus it bubbles the error up.

I have installed the tools, so if I run which from the VS Code terminal I get the following output:

➜ which func
/tmp/fnm-shell-3266999/bin/func

I'm using a Node version manager, fnm specifically, so that may cause an issue, but it's in the path for the built in terminal which I assumed what how vscode executes its checks, or am I mistaken?

If it's not running in context of the shell that boots, is there a way to configure it to run a Node version manager?

[ejizba]

Hmm yeah it sounds like a PATH issue where the VS Code terminal and the child process we use are somehow different. I'll look into a fix on our side.

If you want to work around this, you'll have to figure out where the difference in PATH is. Could be related to a .bashrc or .bash_profile if you have one. If I remember correctly, one of those files doesn't get executed in all cases

[aaronpowell]

After digging through myself it does feel like it's probably a problem of it not being in PATH until the shell rc file is loaded.

Architecturally, is there a reason that you need to have func globally installed rather than a local package and use npx to run it?

[ejizba]

Architecturally, is there a reason that you need to have func globally installed rather than a local package and use npx to run it?

There was never a conscious choice to exclude this scenario. I did a quick prototype and came up with this: https://github.com/EricJizbaMSFT/workspaceFuncCli. I started with a basic JavaScript project and modified it in this commit to use the local package when debugging. It definitely works, but has some room for improvement in terms of "official" support from our extension.

[e14crymer]

Also hitting this challenge. I am afraid I have nothing to add that is not already being said. I am scraping around for a workaround. My only option so far is to use vscode online for debug. Not exactly a fix ;)

[ejizba]

@aaronpowell @e14crymer I still haven't fixed the root cause of this issue, but we just released v0.22.1 of the extension with a setting "azureFunctions.validateFuncCoreTools" that you can set to false as a workaround

[aaronpowell]

Thanks, I'll have a look into it post-Build, but I still think that looking to work with npx would be a good idea, since then you can install the tools locally to the project (which I tend to do anyway) and not rely on a global install.

[e14crymer]

I still get the warning to install Azure Core Functions. I presumed that "azureFunctions.validateFuncCoreTools": true goes in either local.settings.json or settings.json. Neither work for me.

[ejizba]

It's a VS Code Setting. The default is true. If you want to skip validation (aka the validation is a false positive for some reason) you would set it to false