heroku日誌sh：1：併發：未找到

2017-10-08T20:06:11.093118+00:00 heroku[web.1]: Starting process with command `npm start` 
2017-10-08T20:06:15.431068+00:00 app[web.1]: 
2017-10-08T20:06:15.431083+00:00 app[web.1]: > [email protected] start /app 
2017-10-08T20:06:15.431084+00:00 app[web.1]: > concurrently "npm run server" "npm run client" 
2017-10-08T20:06:15.439379+00:00 app[web.1]: sh: 1: concurrently: not found 
2017-10-08T20:06:15.446591+00:00 app[web.1]: npm ERR! file sh 
2017-10-08T20:06:15.431085+00:00 app[web.1]: 
2017-10-08T20:06:15.447135+00:00 app[web.1]: npm ERR! errno ENOENT 
2017-10-08T20:06:15.447368+00:00 app[web.1]: npm ERR! syscall spawn 
2017-10-08T20:06:15.446893+00:00 app[web.1]: npm ERR! code ELIFECYCLE 
2017-10-08T20:06:15.453425+00:00 app[web.1]: npm ERR! 
2017-10-08T20:06:15.448865+00:00 app[web.1]: npm ERR! [email protected] start: `concurrently "npm run server" "npm run client"` 
2017-10-08T20:06:15.453636+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script. 
2017-10-08T20:06:15.464269+00:00 app[web.1]: 
2017-10-08T20:06:15.453115+00:00 app[web.1]: npm ERR! spawn ENOENT 
2017-10-08T20:06:15.453824+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 
2017-10-08T20:06:15.469282+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 
2017-10-08T20:06:15.469426+00:00 app[web.1]: npm ERR!  /app/.npm/_logs/2017-10-08T20_06_15_456Z-debug.log 
2017-10-08T20:06:15.625015+00:00 heroku[web.1]: State changed from starting to crashed 
2017-10-08T20:06:15.627831+00:00 heroku[web.1]: State changed from crashed to starting 
2017-10-08T20:06:15.609086+00:00 heroku[web.1]: Process exited with status 1 
2017-10-08T20:06:20.543684+00:00 heroku[web.1]: Starting process with command `npm start` 
2017-10-08T20:06:23.048216+00:00 heroku[web.1]: Process exited with status 1 
2017-10-08T20:06:22.944636+00:00 app[web.1]: > [email protected] start /app 
2017-10-08T20:06:22.944621+00:00 app[web.1]: 
2017-10-08T20:06:22.944637+00:00 app[web.1]: > concurrently "npm run server" "npm run client" 
2017-10-08T20:06:22.944637+00:00 app[web.1]: 
2017-10-08T20:06:22.951908+00:00 app[web.1]: sh: 1: concurrently: not found 
2017-10-08T20:06:22.957587+00:00 app[web.1]: npm ERR! code ELIFECYCLE 
2017-10-08T20:06:22.957261+00:00 app[web.1]: npm ERR! file sh 
2017-10-08T20:06:22.957843+00:00 app[web.1]: npm ERR! errno ENOENT 
2017-10-08T20:06:22.959735+00:00 app[web.1]: npm ERR! spawn ENOENT 
2017-10-08T20:06:22.958098+00:00 app[web.1]: npm ERR! syscall spawn 
2017-10-08T20:06:22.959544+00:00 app[web.1]: npm ERR! [email protected] start: `concurrently "npm run server" "npm run client"` 
2017-10-08T20:06:22.960008+00:00 app[web.1]: npm ERR! 
2017-10-08T20:06:22.960225+00:00 app[web.1]: npm ERR! Failed at the shopping-c[email protected] start script. 
2017-10-08T20:06:22.966218+00:00 app[web.1]: 
2017-10-08T20:06:22.966570+00:00 app[web.1]: npm ERR!  /app/.npm/_logs/2017-10-08T20_06_22_962Z-debug.log 
2017-10-08T20:06:22.960452+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 
2017-10-08T20:06:22.966432+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 
2017-10-08T20:06:23.060706+00:00 heroku[web.1]: State changed from starting to crashed

我可以在本地主機上運行應用程序，但它在heroku中崩潰。似乎我在使用heroku啓動應用程序時遇到了兼容包問題。我使用了npm i -S concurrently，但它在開發依賴下下載。 Heroku中有一些類型的設置需要同時更改使用嗎？heroku日誌sh：1：併發：未找到

來源

2017-10-09 Jose' C Flores

檢查。您可以初始化一個對象，即使它沒有安裝在依賴項中也不必使用它。我初始化節點郵件程序沒有使用它，它沒有安裝在依賴項中，只有在本地運行得很好。 – zb22

apt-get install nodejs-legacy 
npm install -g tsc 
npm install -g concurrently 
npm install -g typescript

，如果你使用相同的包，當你初始化你的對象試試這個命令

來源

2017-10-10 06:44:54 kumbhanibhavesh

heroku日誌sh：1：併發：未找到

回答

相關問題