Deployed heroku issue

[f-ke]

Hi Basir,
After following your instruction to deploy Heroku, I find I can not deploy it successfully. It seems like it begins with npm start though I have set the Procfile. The log detail is below. Look forward to your suggestion!

npm ERR! file sh
2020-09-29T07:05:48.838186+00:00 app[web.1]: npm ERR! errno ENOENT
2020-09-29T07:05:48.843109+00:00 app[web.1]: npm ERR! amazon@1.0.0 start: nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T07:05:48.843465+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-09-29T07:05:48.843824+00:00 app[web.1]: npm ERR!
2020-09-29T07:05:48.844191+00:00 app[web.1]: npm ERR! Failed at the amazon@1.0.0 start script.
2020-09-29T07:05:48.844720+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T07:05:48.863706+00:00 app[web.1]:
2020-09-29T07:05:48.865150+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T07:05:48.865405+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T07_05_48_854Z-debug.log
2020-09-29T07:05:48.944845+00:00 heroku[web.1]: Process exited with status 1
2020-09-29T07:05:49.032395+00:00 heroku[web.1]: State changed from starting to crashed
2020-09-29T10:19:29.600400+00:00 heroku[web.1]: State changed from crashed to starting
2020-09-29T10:19:31.833484+00:00 heroku[web.1]: Starting process with command npm start
2020-09-29T10:19:34.451984+00:00 app[web.1]:
2020-09-29T10:19:34.452005+00:00 app[web.1]: > amazon@1.0.0 start /app
2020-09-29T10:19:34.452006+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T10:19:34.452006+00:00 app[web.1]:
2020-09-29T10:19:34.456936+00:00 app[web.1]: sh: 1: nodemon: not found
2020-09-29T10:19:34.462828+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-09-29T10:19:34.463090+00:00 app[web.1]: npm ERR! syscall spawn
2020-09-29T10:19:34.463271+00:00 app[web.1]: npm ERR! file sh
2020-09-29T10:19:34.463601+00:00 app[web.1]: npm ERR! errno ENOENT
2020-09-29T10:19:34.466596+00:00 app[web.1]: npm ERR! amazon@1.0.0 start: nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T10:19:34.466753+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-09-29T10:19:34.466958+00:00 app[web.1]: npm ERR!
2020-09-29T10:19:34.467102+00:00 app[web.1]: npm ERR! Failed at the amazon@1.0.0 start script.
2020-09-29T10:19:34.467215+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T10:19:34.477187+00:00 app[web.1]:
2020-09-29T10:19:34.477465+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T10:19:34.477607+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T10_19_34_468Z-debug.log
2020-09-29T10:19:34.551929+00:00 heroku[web.1]: Process exited with status 1
2020-09-29T10:19:34.596023+00:00 heroku[web.1]: State changed from starting to crashed
2020-09-29T15:43:49.551942+00:00 heroku[web.1]: State changed from crashed to starting
2020-09-29T15:43:51.691519+00:00 heroku[web.1]: Starting process with command npm start
2020-09-29T15:43:53.953535+00:00 app[web.1]:
2020-09-29T15:43:53.953576+00:00 app[web.1]: > amazon@1.0.0 start /app
2020-09-29T15:43:53.953577+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T15:43:53.953578+00:00 app[web.1]:
2020-09-29T15:43:53.969880+00:00 app[web.1]: sh: 1: nodemon: not found
2020-09-29T15:43:53.976401+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-09-29T15:43:53.976708+00:00 app[web.1]: npm ERR! syscall spawn
2020-09-29T15:43:53.976912+00:00 app[web.1]: npm ERR! file sh
2020-09-29T15:43:53.977075+00:00 app[web.1]: npm ERR! errno ENOENT
2020-09-29T15:43:53.980254+00:00 app[web.1]: npm ERR! amazon@1.0.0 start: nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T15:43:53.980467+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-09-29T15:43:53.980655+00:00 app[web.1]: npm ERR!
2020-09-29T15:43:53.980837+00:00 app[web.1]: npm ERR! Failed at the amazon@1.0.0 start script.
2020-09-29T15:43:53.985444+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T15:43:53.989704+00:00 app[web.1]:
2020-09-29T15:43:53.990370+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T15:43:53.990905+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T15_43_53_982Z-debug.log
2020-09-29T15:43:54.130302+00:00 heroku[web.1]: Process exited with status 1
2020-09-29T15:43:54.174702+00:00 heroku[web.1]: State changed from starting to crashed
2020-09-29T19:07:44.000000+00:00 app[api]: Build started by user kfan4372@gmail.com
2020-09-29T19:08:11.448979+00:00 app[api]: Deploy d3eeb46a by user kfan4372@gmail.com
2020-09-29T19:08:11.448979+00:00 app[api]: Release v5 created by user kfan4372@gmail.com
2020-09-29T19:08:11.747550+00:00 heroku[web.1]: State changed from crashed to starting
2020-09-29T19:08:12.000000+00:00 app[api]: Build succeeded
2020-09-29T19:08:14.518377+00:00 heroku[web.1]: Starting process with command npm start
2020-09-29T19:08:17.766156+00:00 app[web.1]:
2020-09-29T19:08:17.766177+00:00 app[web.1]: > amazon@1.0.0 start /app
2020-09-29T19:08:17.766178+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T19:08:17.766178+00:00 app[web.1]:
2020-09-29T19:08:17.773799+00:00 app[web.1]: sh: 1: nodemon: not found
2020-09-29T19:08:17.780106+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-09-29T19:08:17.780458+00:00 app[web.1]: npm ERR! syscall spawn
2020-09-29T19:08:17.780731+00:00 app[web.1]: npm ERR! file sh
2020-09-29T19:08:17.781107+00:00 app[web.1]: npm ERR! errno ENOENT
2020-09-29T19:08:17.783896+00:00 app[web.1]: npm ERR! amazon@1.0.0 start: nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T19:08:17.783982+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-09-29T19:08:17.784109+00:00 app[web.1]: npm ERR!
2020-09-29T19:08:17.784209+00:00 app[web.1]: npm ERR! Failed at the amazon@1.0.0 start script.
2020-09-29T19:08:17.784302+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T19:08:17.794604+00:00 app[web.1]:
2020-09-29T19:08:17.794798+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T19:08:17.794904+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T19_08_17_786Z-debug.log
2020-09-29T19:08:17.856758+00:00 heroku[web.1]: Process exited with status 1
2020-09-29T19:08:17.897773+00:00 heroku[web.1]: State changed from starting to crashed
2020-09-29T19:08:17.900441+00:00 heroku[web.1]: State changed from crashed to starting
2020-09-29T19:08:20.435030+00:00 heroku[web.1]: Starting process with command npm start
2020-09-29T19:08:22.998149+00:00 app[web.1]:
2020-09-29T19:08:22.998219+00:00 app[web.1]: > amazon@1.0.0 start /app
2020-09-29T19:08:22.998220+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T19:08:22.998220+00:00 app[web.1]:
2020-09-29T19:08:23.004433+00:00 app[web.1]: sh: 1: nodemon: not found
2020-09-29T19:08:23.016487+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-09-29T19:08:23.016987+00:00 app[web.1]: npm ERR! syscall spawn
2020-09-29T19:08:23.017269+00:00 app[web.1]: npm ERR! file sh
2020-09-29T19:08:23.017563+00:00 app[web.1]: npm ERR! errno ENOENT
2020-09-29T19:08:23.020189+00:00 app[web.1]: npm ERR! amazon@1.0.0 start: nodemon --watch backend --exec babel-node backend/server.js
2020-09-29T19:08:23.020323+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-09-29T19:08:23.020529+00:00 app[web.1]: npm ERR!
2020-09-29T19:08:23.020675+00:00 app[web.1]: npm ERR! Failed at the amazon@1.0.0 start script.
2020-09-29T19:08:23.020802+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-09-29T19:08:23.028392+00:00 app[web.1]:
2020-09-29T19:08:23.028580+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-09-29T19:08:23.031084+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T19_08_23_022Z-debug.log
2020-09-29T19:08:23.077554+00:00 heroku[web.1]: Process exited with status 1
2020-09-29T19:08:23.118698+00:00 heroku[web.1]: State changed from starting to crashed

[basir]

Hello there Ask your questions here https://webacademy.pro

…

On Tue, Sep 29, 2020 at 10:54 PM f-ke ***@***.***> wrote: Hi Basir, After following your instruction to deploy Heroku, I find I can not deploy it successfully. It seems like it begins with npm start though I have set the Procfile. The log detail is below. Look forward to your suggestion! npm ERR! file sh 2020-09-29T07:05:48.838186+00:00 app[web.1]: npm ERR! errno ENOENT 2020-09-29T07:05:48.843109+00:00 app[web.1]: npm ERR! ***@***.*** start: nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T07:05:48.843465+00:00 app[web.1]: npm ERR! spawn ENOENT 2020-09-29T07:05:48.843824+00:00 app[web.1]: npm ERR! 2020-09-29T07:05:48.844191+00:00 app[web.1]: npm ERR! Failed at the ***@***.*** start script. 2020-09-29T07:05:48.844720+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2020-09-29T07:05:48.863706+00:00 app[web.1]: 2020-09-29T07:05:48.865150+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2020-09-29T07:05:48.865405+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T07_05_48_854Z-debug.log 2020-09-29T07:05:48.944845+00:00 heroku[web.1]: Process exited with status 1 2020-09-29T07:05:49.032395+00:00 heroku[web.1]: State changed from starting to crashed 2020-09-29T10:19:29.600400+00:00 heroku[web.1]: State changed from crashed to starting 2020-09-29T10:19:31.833484+00:00 heroku[web.1]: Starting process with command npm start 2020-09-29T10:19:34.451984+00:00 app[web.1]: 2020-09-29T10:19:34.452005+00:00 app[web.1]: > ***@***.*** start /app 2020-09-29T10:19:34.452006+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T10:19:34.452006+00:00 app[web.1]: 2020-09-29T10:19:34.456936+00:00 app[web.1]: sh: 1: nodemon: not found 2020-09-29T10:19:34.462828+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2020-09-29T10:19:34.463090+00:00 app[web.1]: npm ERR! syscall spawn 2020-09-29T10:19:34.463271+00:00 app[web.1]: npm ERR! file sh 2020-09-29T10:19:34.463601+00:00 app[web.1]: npm ERR! errno ENOENT 2020-09-29T10:19:34.466596+00:00 app[web.1]: npm ERR! ***@***.*** start: nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T10:19:34.466753+00:00 app[web.1]: npm ERR! spawn ENOENT 2020-09-29T10:19:34.466958+00:00 app[web.1]: npm ERR! 2020-09-29T10:19:34.467102+00:00 app[web.1]: npm ERR! Failed at the ***@***.*** start script. 2020-09-29T10:19:34.467215+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2020-09-29T10:19:34.477187+00:00 app[web.1]: 2020-09-29T10:19:34.477465+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2020-09-29T10:19:34.477607+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T10_19_34_468Z-debug.log 2020-09-29T10:19:34.551929+00:00 heroku[web.1]: Process exited with status 1 2020-09-29T10:19:34.596023+00:00 heroku[web.1]: State changed from starting to crashed 2020-09-29T15:43:49.551942+00:00 heroku[web.1]: State changed from crashed to starting 2020-09-29T15:43:51.691519+00:00 heroku[web.1]: Starting process with command npm start 2020-09-29T15:43:53.953535+00:00 app[web.1]: 2020-09-29T15:43:53.953576+00:00 app[web.1]: > ***@***.*** start /app 2020-09-29T15:43:53.953577+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T15:43:53.953578+00:00 app[web.1]: 2020-09-29T15:43:53.969880+00:00 app[web.1]: sh: 1: nodemon: not found 2020-09-29T15:43:53.976401+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2020-09-29T15:43:53.976708+00:00 app[web.1]: npm ERR! syscall spawn 2020-09-29T15:43:53.976912+00:00 app[web.1]: npm ERR! file sh 2020-09-29T15:43:53.977075+00:00 app[web.1]: npm ERR! errno ENOENT 2020-09-29T15:43:53.980254+00:00 app[web.1]: npm ERR! ***@***.*** start: nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T15:43:53.980467+00:00 app[web.1]: npm ERR! spawn ENOENT 2020-09-29T15:43:53.980655+00:00 app[web.1]: npm ERR! 2020-09-29T15:43:53.980837+00:00 app[web.1]: npm ERR! Failed at the ***@***.*** start script. 2020-09-29T15:43:53.985444+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2020-09-29T15:43:53.989704+00:00 app[web.1]: 2020-09-29T15:43:53.990370+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2020-09-29T15:43:53.990905+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T15_43_53_982Z-debug.log 2020-09-29T15:43:54.130302+00:00 heroku[web.1]: Process exited with status 1 2020-09-29T15:43:54.174702+00:00 heroku[web.1]: State changed from starting to crashed 2020-09-29T19:07:44.000000+00:00 app[api]: Build started by user ***@***.*** 2020-09-29T19:08:11.448979+00:00 app[api]: Deploy d3eeb46a by user ***@***.*** 2020-09-29T19:08:11.448979+00:00 app[api]: Release v5 created by user ***@***.*** 2020-09-29T19:08:11.747550+00:00 heroku[web.1]: State changed from crashed to starting 2020-09-29T19:08:12.000000+00:00 app[api]: Build succeeded 2020-09-29T19:08:14.518377+00:00 heroku[web.1]: Starting process with command npm start 2020-09-29T19:08:17.766156+00:00 app[web.1]: 2020-09-29T19:08:17.766177+00:00 app[web.1]: > ***@***.*** start /app 2020-09-29T19:08:17.766178+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T19:08:17.766178+00:00 app[web.1]: 2020-09-29T19:08:17.773799+00:00 app[web.1]: sh: 1: nodemon: not found 2020-09-29T19:08:17.780106+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2020-09-29T19:08:17.780458+00:00 app[web.1]: npm ERR! syscall spawn 2020-09-29T19:08:17.780731+00:00 app[web.1]: npm ERR! file sh 2020-09-29T19:08:17.781107+00:00 app[web.1]: npm ERR! errno ENOENT 2020-09-29T19:08:17.783896+00:00 app[web.1]: npm ERR! ***@***.*** start: nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T19:08:17.783982+00:00 app[web.1]: npm ERR! spawn ENOENT 2020-09-29T19:08:17.784109+00:00 app[web.1]: npm ERR! 2020-09-29T19:08:17.784209+00:00 app[web.1]: npm ERR! Failed at the ***@***.*** start script. 2020-09-29T19:08:17.784302+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2020-09-29T19:08:17.794604+00:00 app[web.1]: 2020-09-29T19:08:17.794798+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2020-09-29T19:08:17.794904+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T19_08_17_786Z-debug.log 2020-09-29T19:08:17.856758+00:00 heroku[web.1]: Process exited with status 1 2020-09-29T19:08:17.897773+00:00 heroku[web.1]: State changed from starting to crashed 2020-09-29T19:08:17.900441+00:00 heroku[web.1]: State changed from crashed to starting 2020-09-29T19:08:20.435030+00:00 heroku[web.1]: Starting process with command npm start 2020-09-29T19:08:22.998149+00:00 app[web.1]: 2020-09-29T19:08:22.998219+00:00 app[web.1]: > ***@***.*** start /app 2020-09-29T19:08:22.998220+00:00 app[web.1]: > nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T19:08:22.998220+00:00 app[web.1]: 2020-09-29T19:08:23.004433+00:00 app[web.1]: sh: 1: nodemon: not found 2020-09-29T19:08:23.016487+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2020-09-29T19:08:23.016987+00:00 app[web.1]: npm ERR! syscall spawn 2020-09-29T19:08:23.017269+00:00 app[web.1]: npm ERR! file sh 2020-09-29T19:08:23.017563+00:00 app[web.1]: npm ERR! errno ENOENT 2020-09-29T19:08:23.020189+00:00 app[web.1]: npm ERR! ***@***.*** start: nodemon --watch backend --exec babel-node backend/server.js 2020-09-29T19:08:23.020323+00:00 app[web.1]: npm ERR! spawn ENOENT 2020-09-29T19:08:23.020529+00:00 app[web.1]: npm ERR! 2020-09-29T19:08:23.020675+00:00 app[web.1]: npm ERR! Failed at the ***@***.*** start script. 2020-09-29T19:08:23.020802+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2020-09-29T19:08:23.028392+00:00 app[web.1]: 2020-09-29T19:08:23.028580+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2020-09-29T19:08:23.031084+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-09-29T19_08_23_022Z-debug.log 2020-09-29T19:08:23.077554+00:00 heroku[web.1]: Process exited with status 1 2020-09-29T19:08:23.118698+00:00 heroku[web.1]: State changed from starting to crashed — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#111>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATUFQ63CVVIHMMCD4KSSLDSIIYAJANCNFSM4R6GKL4A> .