charles asked 2 years ago
using dir/s I find node.js installed deep into the vscode directory structure after a scratch install of vscode. But when I try to test for it with node –version I get an error that that node.js nowhere to be found. I suspect there is a pathing problem. After searching around it seems this is a chronic problem with node.js since 2018 with various cures depending on vscode version.. Can you shed light on how to fix access to node.js?
I am used to adding path destinations separated by semicolons but not sure that the environment variables work the same way as in previous versions like windows 7
I am running windows 10 22H2 with latest versions of vscode and platform io
charles answered 2 years ago
I solved the problem by installing Node.js as directed in:
Setting up additional components to use with Visual Studio Code
by downloading and executing the .msi file for the standalone package from nodejs.org
now my test program runs in a vscode workspace, and the following code runs in a terminal in vscode or platformio
C:\Users\cfyte>node –version
v18.13.0
And it only took 6 hours of searching to find the answer.
Sara Santos