npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Npm issue with deployment on cloud foundry

        2019-02-21T11:08:43.59-0500 [API/3] OUT Created app with guid f437c01c-0fc7-4b3f-8456-0d99bcccd9a5
      2019-02-21T11:09:23.42-0500 [API/1] OUT Uploading bits for app with guid f437c01c-0fc7-4b3f-8456-0d99bcccd9a5
 2019-02-21T11:10:20.06-0500 [API/0] OUT Creating build for app with guid f437c01c-0fc7-4b3f-8456- 
2019-02-21T11:10:20.35-0500 [API/0] OUT Updated app with guid f437c01c-0fc7-4b3f-8456- 
0d99bcccd9a5 ({"state"=>"STARTED"})
2019-02-21T11:13:20.38-0500 [API/3] OUT Creating droplet for app with guid f437c01c-0fc7-4b3f- 
2019-02-21T11:13:31.86-0500 [CELL/0] OUT Cell 0a236bb2-d6ed-4da1-b868-0b176cba1e79 creating 
container for instance e0e47c73-1d7b-47a7-5e5f-17e8
2019-02-21T11:13:32.18-0500 [CELL/0] OUT Cell 0a236bb2-d6ed-4da1-b868-0b176cba1e79 
successfully created container for instance e0e47c73-1d7b-47a7-5e5f-17e8
2019-02-21T11:13:37.39-0500 [CELL/0] OUT Starting health monitoring of container
2019-02-21T11:13:38.25-0500 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.4.0-138-generic
2019-02-21T11:13:38.25-0500 [APP/PROC/WEB/0] ERR npm ERR! argv 
"/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
2019-02-21T11:13:38.25-0500 [APP/PROC/WEB/0] ERR npm ERR! node v6.14.2
2019-02-21T11:13:38.25-0500 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
2019-02-21T11:13:38.26-0500 [APP/PROC/WEB/0] ERR npm ERR! missing script: start
2019-02-21T11:13:38.26-0500 [APP/PROC/WEB/0] ERR npm ERR! 
 2019-02-21T11:13:38.26-0500 [APP/PROC/WEB/0] ERR npm ERR! If you need help, you may report 
this error at: 2019-02-21T11:13:38.26-0500 [APP/PROC/WEB/0] ERR npm ERR! 
2019-02-21T11:13:38.27-0500 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file 
with any support request:
 2019-02-21T11:13:38.27-0500 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm- 
2019-02-21T11:13:38.29-0500 [APP/PROC/WEB/0] OUT Exit status 1
2019-02-21T11:13:38.30-0500 [CELL/SSHD/0] OUT Exit status 0
2019-02-21T11:13:38.47-0500 [CELL/0] OUT Cell 0a236bb2-d6ed-4da1-b868-0b176cba1e79 stopping 
instance e0e47c73-1d7b-47a7-5e5f-17e8
2019-02-21T11:13:38.47-0500 [CELL/0] OUT Cell 0a236bb2-d6ed-4da1-b868-0b176cba1e79 
destroying container for instance e0e47c73-1d7b-47a7-5e5f-17e8
2019-02-21T11:13:39.50-0500 [CELL/0] OUT Cell 0a236bb2-d6ed-4da1-b868-0b176cba1e79 
successfully destroyed container for instance e0e47c73-1d7b-47a7-5e5f-17e8
2019-02-21T11:13:41.45-0500 [APP/PROC/WEB/0] OUT Exit status 1
2019-02-21T11:13:41.45-0500 [CELL/SSHD/0] OUT Exit status 0
2019-02-21T11:13:41.58-0500 [CELL/0] OUT Cell caa1867a-b432-41a1-a429-644f73a1408c stopping 
instance c4f9b9be-1d16-4e17-6994-d172
2019-02-21T11:13:41.58-0500 [CELL/0] OUT Cell caa1867a-b432-41a1-a429-644f73a1408c 
destroying container for instance c4f9b9be-1d16-4e17-6994-d172
2019-02-21T11:13:41.62-0500 [API/3] OUT Process has crashed with type: "web"
2019-02-21T11:13:41.63-0500 [API/3] OUT App instance exited with guid f437c01c-0fc7-4b3f-8456- 
0d99bcccd9a5 payload: {"instance"=>"c4f9b9be-1d16-4e17-6994-d172", "index"=>0, 
"reason"=>"CRASHED", "exit_description"=>"APP/PROC/WEB: Exited with status 1", 
"crash_count"=>3, "crash_timestamp"=>1550765621576288168, "version"=>"db5e8cef-0242-4a97- 

The deployment is calling npm run start on your package. npm looks in the package.json for a “scripts” entry called start, or for a server.js file the root of your package. It isn’t finding either.