Apr 22 03:46:03 AM ==> It looks like we don’t have access to your repo, but we’ll try to clone it anyway.
Apr 22 03:46:03 AM ==> Cloning from GitHub - Vivek0000singh/vivekcs62…
Apr 22 03:46:03 AM ==> Checking out commit faf04871a92aa027493fbbb49927040acedfcb37 in branch main
Apr 22 03:46:07 AM ==> Running build command ‘npm install’…
Apr 22 03:46:10 AM added 83 packages from 104 contributors and audited 83 packages in 2.349s
Apr 22 03:46:10 AM
Apr 22 03:46:10 AM 8 packages are looking for funding
Apr 22 03:46:10 AM run npm fund for details
Apr 22 03:46:10 AM
Apr 22 03:46:10 AM found 0 vulnerabilities
Apr 22 03:46:10 AM
Apr 22 03:46:10 AM ==> Generating container image from build. This may take a few minutes…
Apr 22 03:47:05 AM ==> Uploading build…
Apr 22 03:47:28 AM ==> Build uploaded in 20s
Apr 22 03:47:29 AM ==> Build successful 
Apr 22 03:47:29 AM ==> Deploying…
Apr 22 03:47:41 AM ==> Starting service with ‘npm run dev’
Apr 22 03:47:44 AM
Apr 22 03:47:44 AM > backend_sanity@1.0.0 dev /opt/render/project/src/backend_sanity
Apr 22 03:47:44 AM > nodemon
Apr 22 03:47:44 AM
Apr 22 03:47:44 AM sh: 1: nodemon: not found
Apr 22 03:47:44 AM npm ERR! code ELIFECYCLE
Apr 22 03:47:44 AM npm ERR! syscall spawn
Apr 22 03:47:44 AM npm ERR! file sh
Apr 22 03:47:44 AM npm ERR! errno ENOENT
Apr 22 03:47:44 AM npm ERR! backend_sanity@1.0.0 dev: nodemon
Apr 22 03:47:44 AM npm ERR! spawn ENOENT
Apr 22 03:47:44 AM npm ERR!
Apr 22 03:47:44 AM npm ERR! Failed at the backend_sanity@1.0.0 dev script.
Hi,
The error here seems to be:
nodemon: not found
You’d need to check this was listed as a dependency and installed correctly
As an aside, nodemon isn’t necessary for production apps on Render, just run your code directly, e.g. node index.js.
Alan
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.