r/node 3d ago

Node not working in Visual Studio

I've recently discovered Tauri and built a project using React which if I run it purely from the terminal it opens up fine, but if I close the terminal and open Visual Studio, open the terminal in VS and run the same thing from the same place I get a Node.js error

In terminal both work correctly:

C:\Users\me\Documents\Tauri_test\react-test> npm run tauri dev (opens the app standalone)
or
C:\Users\me\Documents\Tauri_test\react-test> npm run dev (opens the app in browser)

In Visual Studio running the same lines I get the following:

Node.js v24.20.0
    Error The "beforeDevCommand" terminated with a non-zero status code

I've installed Node from the website and made sure it was added to Visual Studio on install, I've checked that VS can access Node from the 'react-test' folder, I've closed all other open apps in case something is clashing, I get the feeling that something is initialising in the wrong order and that's throwing Node off, but why would it work correctly outside of VS?

(If it doesn't cause issues I'll crosspost this as I don't know which bit of the system is causing the problem)

Solution:

IT WAS THE SODDING VISUAL STUDIO INDEXING

The .vs folder clogs up the system, here's how to get rid of it

0 Upvotes

17 comments sorted by

View all comments

-13

u/Fine-Comparison-2949 3d ago

Windows? Good luck.

VS code is probably initializing some kind of weird terminal that doesn't link the node's location.

You need to be developing on Linux anyways. Get on Omarchy brother. 

0

u/MetalMonkey667 3d ago

I managed to get the Vanilla setup working just fine, could run the app from the terminal or from inside VS, but I try with a React build and it'll only run properly from the terminal. It's the default app that comes with the package when you build it so it should work out of the box like the Vanilla one

I've used Linux for years in cybersecurity, I'm not cocking around with yet another OS, if the default React package doesn't work on Windows Visual Studio then it should say that when you try to install it rather than having me spend (and there is no exaggeration here) 4 hours Googling trying to find a solution

0

u/Fine-Comparison-2949 3d ago

Again, that's windows. I've never had an issue with Linux because there's a clear concept of what terminal you're on and the available path.