You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2020-05-24T11:14:46.401373+00:00 app[web.1]: npm ERR! syscall spawn
2020-05-24T11:14:46.401653+00:00 app[web.1]: npm ERR! file sh
2020-05-24T11:14:46.401945+00:00 app[web.1]: npm ERR! errno ENOENT
2020-05-24T11:14:46.403473+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start: ng serve
2020-05-24T11:14:46.403686+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-05-24T11:14:46.403926+00:00 app[web.1]: npm ERR!
2020-05-24T11:14:46.404158+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T11:14:46.404357+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T11:14:46.411650+00:00 app[web.1]:
2020-05-24T11:14:46.412112+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T11:14:46.412293+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T11_14_46_405Z-debug.log
2020-05-24T11:14:46.490154+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T11:14:46.553525+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T11:14:55.068135+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=e93f0805-5403-4428-b465-ef41d71b4f2b fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:14:56.061638+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=0af7827d-1b33-4140-bb84-8496a44d3ef5 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:19:45.820827+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=572f7a07-ed6f-49a2-b4c0-aafbd6e8d748 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:19:46.694517+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=b8bd1765-5209-4f3c-b59d-ea5b6c54685e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:22:34.045837+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=a30d5939-d30a-47ee-99f3-6660d3dcd10e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:22:34.864431+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=9a43e8c5-4d23-4705-813b-52eb11eff243 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:36:57.151163+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T11:37:06.041016+00:00 heroku[web.1]: Starting process with command npm start
2020-05-24T11:37:08.309212+00:00 app[web.1]:
2020-05-24T11:37:08.309224+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T11:37:08.309224+00:00 app[web.1]: > ng serve
2020-05-24T11:37:08.309224+00:00 app[web.1]:
2020-05-24T11:37:08.315208+00:00 app[web.1]: sh: 1: ng: not found
2020-05-24T11:37:08.319019+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T11:37:08.319200+00:00 app[web.1]: npm ERR! syscall spawn
2020-05-24T11:37:08.319380+00:00 app[web.1]: npm ERR! file sh
2020-05-24T11:37:08.319524+00:00 app[web.1]: npm ERR! errno ENOENT
2020-05-24T11:37:08.320543+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start: ng serve
2020-05-24T11:37:08.320628+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-05-24T11:37:08.320735+00:00 app[web.1]: npm ERR!
2020-05-24T11:37:08.320824+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T11:37:08.320910+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T11:37:08.328064+00:00 app[web.1]:
2020-05-24T11:37:08.328285+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T11:37:08.328462+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T11_37_08_321Z-debug.log
2020-05-24T11:37:08.381518+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T11:37:08.427787+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:00:28.142795+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=26aacaee-9a5b-45ce-8637-c3b447df5522 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:00:29.981044+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=9673e486-e33e-4777-81d0-05146b975df2 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:03:12.231332+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=4543fff3-ceca-4092-98fb-7a9ec4c3ce97 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:03:13.088486+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=e096b90e-790c-4345-bf3e-e08802eb9031 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:06:23.000000+00:00 app[api]: Build started by user tusharbeldiya145@gmail.com
2020-05-24T12:09:51.954412+00:00 app[api]: Deploy 6a41c9ec by user tusharbeldiya145@gmail.com
2020-05-24T12:09:51.954412+00:00 app[api]: Release v4 created by user tusharbeldiya145@gmail.com
2020-05-24T12:09:52.305954+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T12:10:04.000000+00:00 app[api]: Build succeeded
2020-05-24T12:10:05.869198+00:00 heroku[web.1]: Starting process with command npm start
2020-05-24T12:10:08.261374+00:00 app[web.1]:
2020-05-24T12:10:08.261397+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T12:10:08.261398+00:00 app[web.1]: > ng serve
2020-05-24T12:10:08.261398+00:00 app[web.1]:
2020-05-24T12:10:08.383060+00:00 app[web.1]: As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
2020-05-24T12:10:08.383062+00:00 app[web.1]: which will only support Node 6.9 and greater. This package will be officially deprecated
2020-05-24T12:10:08.383063+00:00 app[web.1]: shortly after.
2020-05-24T12:10:08.383063+00:00 app[web.1]:
2020-05-24T12:10:08.383063+00:00 app[web.1]: To disable this warning use "ng set --global warnings.packageDeprecation=false".
2020-05-24T12:10:08.383063+00:00 app[web.1]:
2020-05-24T12:10:08.645776+00:00 app[web.1]: You have to be inside an angular-cli project in order to use the serve command.
2020-05-24T12:10:08.662017+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T12:10:08.662396+00:00 app[web.1]: npm ERR! errno 1
2020-05-24T12:10:08.664057+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start: ng serve
2020-05-24T12:10:08.664276+00:00 app[web.1]: npm ERR! Exit status 1
2020-05-24T12:10:08.664503+00:00 app[web.1]: npm ERR!
2020-05-24T12:10:08.664693+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T12:10:08.664861+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T12:10:08.672572+00:00 app[web.1]:
2020-05-24T12:10:08.673266+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T12:10:08.673267+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T12_10_08_666Z-debug.log
2020-05-24T12:10:08.735583+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T12:10:08.782654+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:10:08.785031+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T12:10:23.333653+00:00 heroku[web.1]: Starting process with command npm start
2020-05-24T12:10:26.159098+00:00 app[web.1]:
2020-05-24T12:10:26.159115+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T12:10:26.159116+00:00 app[web.1]: > ng serve
2020-05-24T12:10:26.159116+00:00 app[web.1]:
2020-05-24T12:10:26.352946+00:00 app[web.1]: As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
2020-05-24T12:10:26.352947+00:00 app[web.1]: which will only support Node 6.9 and greater. This package will be officially deprecated
2020-05-24T12:10:26.352948+00:00 app[web.1]: shortly after.
2020-05-24T12:10:26.352948+00:00 app[web.1]:
2020-05-24T12:10:26.352949+00:00 app[web.1]: To disable this warning use "ng set --global warnings.packageDeprecation=false".
2020-05-24T12:10:26.352949+00:00 app[web.1]:
2020-05-24T12:10:26.767573+00:00 app[web.1]: You have to be inside an angular-cli project in order to use the serve command.
2020-05-24T12:10:26.782118+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T12:10:26.786134+00:00 app[web.1]: npm ERR! errno 1
2020-05-24T12:10:26.794262+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start: ng serve
2020-05-24T12:10:26.794503+00:00 app[web.1]: npm ERR! Exit status 1
2020-05-24T12:10:26.794781+00:00 app[web.1]: npm ERR!
2020-05-24T12:10:26.794994+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T12:10:26.795207+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T12:10:26.817149+00:00 app[web.1]:
2020-05-24T12:10:26.817652+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T12:10:26.817913+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T12_10_26_796Z-debug.log
2020-05-24T12:10:26.877508+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T12:10:26.932900+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:10:27.442970+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=44c409a3-cc4d-4ecd-aa76-ceca72edcb6e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:10:28.243875+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=90c5c2cb-936e-426b-8a8a-efb0eed67d45 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
The text was updated successfully, but these errors were encountered:
2020-05-24T11:14:46.401373+00:00 app[web.1]: npm ERR! syscall spawn
2020-05-24T11:14:46.401653+00:00 app[web.1]: npm ERR! file sh
2020-05-24T11:14:46.401945+00:00 app[web.1]: npm ERR! errno ENOENT
2020-05-24T11:14:46.403473+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start:
ng serve
2020-05-24T11:14:46.403686+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-05-24T11:14:46.403926+00:00 app[web.1]: npm ERR!
2020-05-24T11:14:46.404158+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T11:14:46.404357+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T11:14:46.411650+00:00 app[web.1]:
2020-05-24T11:14:46.412112+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T11:14:46.412293+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T11_14_46_405Z-debug.log
2020-05-24T11:14:46.490154+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T11:14:46.553525+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T11:14:55.068135+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=e93f0805-5403-4428-b465-ef41d71b4f2b fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:14:56.061638+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=0af7827d-1b33-4140-bb84-8496a44d3ef5 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:19:45.820827+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=572f7a07-ed6f-49a2-b4c0-aafbd6e8d748 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:19:46.694517+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=b8bd1765-5209-4f3c-b59d-ea5b6c54685e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:22:34.045837+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=a30d5939-d30a-47ee-99f3-6660d3dcd10e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:22:34.864431+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=9a43e8c5-4d23-4705-813b-52eb11eff243 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T11:36:57.151163+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T11:37:06.041016+00:00 heroku[web.1]: Starting process with command
npm start
2020-05-24T11:37:08.309212+00:00 app[web.1]:
2020-05-24T11:37:08.309224+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T11:37:08.309224+00:00 app[web.1]: > ng serve
2020-05-24T11:37:08.309224+00:00 app[web.1]:
2020-05-24T11:37:08.315208+00:00 app[web.1]: sh: 1: ng: not found
2020-05-24T11:37:08.319019+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T11:37:08.319200+00:00 app[web.1]: npm ERR! syscall spawn
2020-05-24T11:37:08.319380+00:00 app[web.1]: npm ERR! file sh
2020-05-24T11:37:08.319524+00:00 app[web.1]: npm ERR! errno ENOENT
2020-05-24T11:37:08.320543+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start:
ng serve
2020-05-24T11:37:08.320628+00:00 app[web.1]: npm ERR! spawn ENOENT
2020-05-24T11:37:08.320735+00:00 app[web.1]: npm ERR!
2020-05-24T11:37:08.320824+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T11:37:08.320910+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T11:37:08.328064+00:00 app[web.1]:
2020-05-24T11:37:08.328285+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T11:37:08.328462+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T11_37_08_321Z-debug.log
2020-05-24T11:37:08.381518+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T11:37:08.427787+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:00:28.142795+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=26aacaee-9a5b-45ce-8637-c3b447df5522 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:00:29.981044+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=9673e486-e33e-4777-81d0-05146b975df2 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:03:12.231332+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=4543fff3-ceca-4092-98fb-7a9ec4c3ce97 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:03:13.088486+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=e096b90e-790c-4345-bf3e-e08802eb9031 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:06:23.000000+00:00 app[api]: Build started by user tusharbeldiya145@gmail.com
2020-05-24T12:09:51.954412+00:00 app[api]: Deploy 6a41c9ec by user tusharbeldiya145@gmail.com
2020-05-24T12:09:51.954412+00:00 app[api]: Release v4 created by user tusharbeldiya145@gmail.com
2020-05-24T12:09:52.305954+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T12:10:04.000000+00:00 app[api]: Build succeeded
2020-05-24T12:10:05.869198+00:00 heroku[web.1]: Starting process with command
npm start
2020-05-24T12:10:08.261374+00:00 app[web.1]:
2020-05-24T12:10:08.261397+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T12:10:08.261398+00:00 app[web.1]: > ng serve
2020-05-24T12:10:08.261398+00:00 app[web.1]:
2020-05-24T12:10:08.383060+00:00 app[web.1]: As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
2020-05-24T12:10:08.383062+00:00 app[web.1]: which will only support Node 6.9 and greater. This package will be officially deprecated
2020-05-24T12:10:08.383063+00:00 app[web.1]: shortly after.
2020-05-24T12:10:08.383063+00:00 app[web.1]:
2020-05-24T12:10:08.383063+00:00 app[web.1]: To disable this warning use "ng set --global warnings.packageDeprecation=false".
2020-05-24T12:10:08.383063+00:00 app[web.1]:
2020-05-24T12:10:08.645776+00:00 app[web.1]: You have to be inside an angular-cli project in order to use the serve command.
2020-05-24T12:10:08.662017+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T12:10:08.662396+00:00 app[web.1]: npm ERR! errno 1
2020-05-24T12:10:08.664057+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start:
ng serve
2020-05-24T12:10:08.664276+00:00 app[web.1]: npm ERR! Exit status 1
2020-05-24T12:10:08.664503+00:00 app[web.1]: npm ERR!
2020-05-24T12:10:08.664693+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T12:10:08.664861+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T12:10:08.672572+00:00 app[web.1]:
2020-05-24T12:10:08.673266+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T12:10:08.673267+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T12_10_08_666Z-debug.log
2020-05-24T12:10:08.735583+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T12:10:08.782654+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:10:08.785031+00:00 heroku[web.1]: State changed from crashed to starting
2020-05-24T12:10:23.333653+00:00 heroku[web.1]: Starting process with command
npm start
2020-05-24T12:10:26.159098+00:00 app[web.1]:
2020-05-24T12:10:26.159115+00:00 app[web.1]: > ng-app@0.0.0 start /app
2020-05-24T12:10:26.159116+00:00 app[web.1]: > ng serve
2020-05-24T12:10:26.159116+00:00 app[web.1]:
2020-05-24T12:10:26.352946+00:00 app[web.1]: As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
2020-05-24T12:10:26.352947+00:00 app[web.1]: which will only support Node 6.9 and greater. This package will be officially deprecated
2020-05-24T12:10:26.352948+00:00 app[web.1]: shortly after.
2020-05-24T12:10:26.352948+00:00 app[web.1]:
2020-05-24T12:10:26.352949+00:00 app[web.1]: To disable this warning use "ng set --global warnings.packageDeprecation=false".
2020-05-24T12:10:26.352949+00:00 app[web.1]:
2020-05-24T12:10:26.767573+00:00 app[web.1]: You have to be inside an angular-cli project in order to use the serve command.
2020-05-24T12:10:26.782118+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-24T12:10:26.786134+00:00 app[web.1]: npm ERR! errno 1
2020-05-24T12:10:26.794262+00:00 app[web.1]: npm ERR! ng-app@0.0.0 start:
ng serve
2020-05-24T12:10:26.794503+00:00 app[web.1]: npm ERR! Exit status 1
2020-05-24T12:10:26.794781+00:00 app[web.1]: npm ERR!
2020-05-24T12:10:26.794994+00:00 app[web.1]: npm ERR! Failed at the ng-app@0.0.0 start script.
2020-05-24T12:10:26.795207+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-24T12:10:26.817149+00:00 app[web.1]:
2020-05-24T12:10:26.817652+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-24T12:10:26.817913+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-05-24T12_10_26_796Z-debug.log
2020-05-24T12:10:26.877508+00:00 heroku[web.1]: Process exited with status 1
2020-05-24T12:10:26.932900+00:00 heroku[web.1]: State changed from starting to crashed
2020-05-24T12:10:27.442970+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-waters-50542.herokuapp.com request_id=44c409a3-cc4d-4ecd-aa76-ceca72edcb6e fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
2020-05-24T12:10:28.243875+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-waters-50542.herokuapp.com request_id=90c5c2cb-936e-426b-8a8a-efb0eed67d45 fwd="1.38.164.254" dyno= connect= service= status=503 bytes= protocol=https
The text was updated successfully, but these errors were encountered: