Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By Gabor Rendes
We have a NestJS based backend using the App Platform.
Deployments were working fine until today, where we got the following error during build:
[2024-01-10 14:23:15] │ Running custom build command: yarn build
[2024-01-10 14:23:15] │ yarn run v1.22.21
[2024-01-10 14:23:15] │ $ rimraf dist
[2024-01-10 14:23:17] │ $ nest build
[2024-01-10 14:23:17] │ /bin/sh: 1: nest: not found
[2024-01-10 14:23:17] │ error Command failed with exit code 127.
[2024-01-10 14:23:17] │ info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[2024-01-10 14:23:17] │ building: exit status 127
[2024-01-10 14:23:17] │ ERROR: failed to build: exit status 1
What have been changed / what should we change? (Force deployment with clean caches have not worked)
It’s really puzzling since we have a quite identical “test” environment where everything works fine, even after this error occurred, with forced rebuild & clean caches as well.
I have read somewhere that the “@nestjs/cli” would not work as “devDependency” but as a regular “dependency” (and this sound as a plausible reason), but why have not occurred then this error way before?
Any hint / help is really appreciated :) Gabor
jhonnydepp12
dolphinnn
Vaishnavi Vundyala
016512ea60864da0867e5280f293de
Peter Monadjemi
Prince7hakur
devjk1
fc9acbfbc3124cbf8df28a1c5c5cdb
ab871885551143798f41908c709271
gouskova
Saivion Services