[Bug]: VSCode extension fails to find node or tsp-server in PATH about cadl HOT 5 CLOSED

Logic playwright extension uses for finding node instead of just relying on node spawn to work https://github.com/microsoft/playwright-vscode/blob/2eef642e466bd6d216082571f07434a6a7653bcb/src/utils.ts#L144

from cadl.

@JanStevens , I tried to prepare the environment with the steps above but can't repro the issue. From the log, it's because the node can't be found properly, could you help to check whether 'node' can be found from vscode properly? or is there any other special things in your env that may cause vscode can't find 'node'? thanks.

from cadl.

@RodgeFu Hi, I noticed that everything works if you start VSCode with code . in the typespec directory.

When you then close VSCode and open the project from the VSCode menu it does not work anymore. In the terminal view from VSCode node and typespec are always resolved correctly

from cadl.

@JanStevens , do you mean it doesn't work when you start vscode outside shell? could you double check whether you have set the default shell and shims properly? i.e. I can repro the issue when i removed the call to #eval "$(mise activate bash --shims)" in my ~/.profile, which I think is because the mise shims directory is not added to PATH properly, then vscode extension can't find the node. thanks.

from cadl.

Close as this looks like an environment issue. Feel free to reopen if you get more insights about the repro env. thanks.

from cadl.