Kevin Procopio
06/18/2022, 7:52 PMDeploying 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?Frank
sst start
directly in terminal? (without WSL)Kevin Procopio
06/18/2022, 10:33 PM--global
, --local
are deprecated. Use --location=global
instead.
npm ERR! could not determine executable to runKevin Procopio
06/18/2022, 10:34 PMFrank
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?Kevin Procopio
06/20/2022, 3:51 PM