@idan says

@joaomoreno, so happy to have run across this issue after tearing all my hair out trying to understand why my extensions had a path of /usr/bin:/bin:/usr/sbin:/sbin. I'm on OSX, fish 2.5.0., 1.14.0.

Getting the same behavior as @lunaryorn above — removing the -i or changing the spawn's stdio to ['pipe', 'pipe', process.stderr] results in returned output containing the correct PATH. If I dig into result.envPairs it's still PATH=/usr/bin:/bin:/usr/sbin:/sbin though, I don't grok what's going on there.

This is causing the vscode flow extension to blow up, claiming that node isn't in the PATH, because node isn't installed in any one of /usr/bin:/bin:/usr/sbin:/sbin.

I tried the insiders build you linked in your last comment here, but it doesn't seem to solve anything. Any pointers on how I can try running a build with the changes from #29864? Do I just need to figure out how to build VSCode? Are there any shortcuts there?

Thanks for all of your hard work on this — it's really appreciated! ✨ 🍰