I'm having an issue where I get the following error

Deploying stacks
Error: ENOENT: no such file or directory, uv_cwd
at process.wrappedCwd (node:internal/bootstrap/switches/does_own_process_state:126:28)
...

It occurs whenever I make a change to any code. I'm running sst in WSL on Windows, using VSCode. If I restart my machine it will let me do a deployment, but as soon as I make a new edit to the lambda.py code (either via vim or VSCode), the error recurs. Any idea why this is the case?

Hey @Kevin Procopio, do u get the same error if you ran

sst start

directly in terminal? (without WSL)

I get a totally different error: npm WARN config global

--global

,

--local

are deprecated. Use

--location=global

instead. npm ERR! could not determine executable to run

Oh just to clarify: • with WSL,

sst start

fails when u make an edit, but

sst deploy

works • without WSL,

sst start

works, but

sst deploy

fails with error “could not determine executable to run” Is that right?

Not quite. With WSL, sst start works when I make an edit, but sst deploy fails (unless I restart my computer and then run it with no edits, when it works). Without WSL, both commands fail.