compose: BUG spawn serverless ENOENT

I’ve been waiting for this kind of feature, thanks for it ! I just would like to report a bug which I’ve found a workaround, but maybe you could find a real fix.

I’m on a Windows 11, and I’ve installed serverless and @serverless/compose using npm -g.

Everything works fine on each single service, but when I try to deploy using compose, I got the following error :

$ serverless deploy
Deploying to stage dev
auction-service › error › 0s
spawn serverless ENOENT
auth-service › error › 0s
spawn serverless ENOENT
notification-service › error › 0s
spawn serverless ENOENT

My compose file looks like this :

Deploying to stage dev
auction-service › waiting
auth-service › waiting
notification-service › waiting
auction-service › deploying
auth-service › deploying
notification-service › deploying
auction-service › Running "serverless deploy --stage dev"
auth-service › Running "serverless deploy --stage dev"
notification-service › Running "serverless deploy --stage dev"
auction-service › error
auction-service › spawn serverless ENOENT
auction-service › Error: spawn serverless ENOENT
auction-service ›     at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
auction-service ›     at onErrorNT (node:internal/child_process:477:16)
auction-service ›     at processTicksAndRejections (node:internal/process/task_queues:83:21)
auth-service › error
auth-service › spawn serverless ENOENT
auth-service › Error: spawn serverless ENOENT
auth-service ›     at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
auth-service ›     at onErrorNT (node:internal/child_process:477:16)
auth-service ›     at processTicksAndRejections (node:internal/process/task_queues:83:21)
notification-service › error
notification-service › spawn serverless ENOENT
notification-service › Error: spawn serverless ENOENT
notification-service ›     at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
notification-service ›     at onErrorNT (node:internal/child_process:477:16)
notification-service ›     at processTicksAndRejections (node:internal/process/task_queues:83:21)

My workaround was to install serverless using choco in addition to npm -g Removing serverless in npm -g to only use choco serverless is not working neither, I really need to have npm -g and choco serverless.

Hope you guys can find a solution, either way keep up with the great work, this package is amazing !