Worker not finding `node` in a machine that has it installed
Author: JeandccCreated Jul 16, 2025Updated Aug 27, 2026
Labelswindows
I have a Lambda function that when called through sst dev it gives me the error 'node' is not recognized as an internal or external command in a machine that clearly has it, as it was through that machine that I ran sst dev.
Here are the logs with sst dev --print-logs
time=2025-07-16T17:04:46.607-03:00 level=INFO msg="worker died" service=aws.function workerID=4c6b107c801f47a499f1fe8fe5676629
time=2025-07-16T17:04:46.608-03:00 level=INFO msg="deleting worker" service=aws.function workerID=4c6b107c801f47a499f1fe8fe5676629
time=2025-07-16T17:04:48.340-03:00 level=INFO msg="INFO msg service=appsync.connection type=data id=019814d4efe48e9067e2291f"
time=2025-07-16T17:04:48.340-03:00 level=INFO msg="got packet" id=019814d6f127900a8a3846c2 type=0 from=7a9483080f9545ff853e11f63e37dae3
time=2025-07-16T17:04:48.340-03:00 level=INFO msg="worker init" service=aws.function workerID=7a9483080f9545ff853e11f63e37dae3 functionID=ProtectedApiRouterRouteEnvdwoHandler
time=2025-07-16T17:04:48.340-03:00 level=INFO msg="running function" runtime=nodejs20.x functionID=ProtectedApiRouterRouteEnvdwoHandler
time=2025-07-16T17:04:48.341-03:00 level=INFO msg="starting worker" server=localhost:13557/lambda/7a9483080f9545ff853e11f63e37dae3
| +2562047h 'node' is not recognized as an internal or external command,
| +2562047h operable program or batch file.
time=2025-07-16T17:04:48.350-03:00 level=INFO msg="worker died" service=aws.function workerID=7a9483080f9545ff853e11f63e37dae3
time=2025-07-16T17:04:48.350-03:00 level=INFO msg="deleting worker" service=aws.function workerID=7a9483080f9545ff853e11f63e37dae3Environment
- Windows 11
- Node 22.17.1
Source: anomalyco/sst