"index.js not found" when running npm start, ERR! code ELIFECYCLE and ENOENT - node.js

I'm trying to run a Discord bot via Heroku (will this work or is the whole idea flawed?)
However, I receive npm error codes every time I run npm start, and the bot remains offline on Discord.
I have already tried npm cache clean --force,
rmdir /S /Q node_modules and npm install, but none of these worked.
Here are the console logs:
2021-05-09T11:37:13.225562+00:00 heroku[web.1]: Process exited with status 1
2021-05-09T11:37:13.398582+00:00 heroku[web.1]: State changed from starting to crashed
2021-05-09T11:37:20.322275+00:00 app[api]: Starting process with command `npm start` by user <email redacted>
2021-05-09T11:37:23.274907+00:00 heroku[run.4911]: State changed from starting to up
2021-05-09T11:37:23.427148+00:00 heroku[run.4911]: Awaiting client
2021-05-09T11:37:23.726119+00:00 heroku[run.4911]: Starting process with command `npm start`
2021-05-09T11:37:28.678579+00:00 heroku[run.4911]: Process exited with status 1
2021-05-09T11:37:28.742179+00:00 heroku[run.4911]: State changed from up to complete
2021-05-09T11:44:03.004685+00:00 heroku[web.1]: State changed from crashed to starting
2021-05-09T11:44:05.335454+00:00 heroku[web.1]: Starting process with command `npm start`
2021-05-09T11:44:08.088534+00:00 heroku[web.1]: Process exited with status 1
2021-05-09T11:44:08.229000+00:00 heroku[web.1]: State changed from starting to crashed
2021-05-09T11:44:08.232296+00:00 heroku[web.1]: State changed from crashed to starting
2021-05-09T11:44:08.000901+00:00 app[web.1]:
2021-05-09T11:44:08.000925+00:00 app[web.1]: > CalculatorBot#1.0.0 start /app
2021-05-09T11:44:08.000925+00:00 app[web.1]: > index.js
2021-05-09T11:44:08.000925+00:00 app[web.1]:
2021-05-09T11:44:08.005333+00:00 app[web.1]: sh: 1: index.js: not found
2021-05-09T11:44:08.012134+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-05-09T11:44:08.012381+00:00 app[web.1]: npm ERR! syscall spawn
2021-05-09T11:44:08.012474+00:00 app[web.1]: npm ERR! file sh
2021-05-09T11:44:08.012618+00:00 app[web.1]: npm ERR! errno ENOENT
2021-05-09T11:44:08.016105+00:00 app[web.1]: npm ERR! CalculatorBot#1.0.0 start: `index.js`
2021-05-09T11:44:08.016163+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-05-09T11:44:08.016238+00:00 app[web.1]: npm ERR!
2021-05-09T11:44:08.016285+00:00 app[web.1]: npm ERR! Failed at the CalculatorBot#1.0.0 start script.
2021-05-09T11:44:08.016364+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-05-09T11:44:08.024564+00:00 app[web.1]:
2021-05-09T11:44:08.024647+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-05-09T11:44:08.024701+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-05-09T11_44_08_016Z-debug.log
2021-05-09T11:44:11.422108+00:00 heroku[web.1]: Starting process with command `npm start`
2021-05-09T11:44:14.301131+00:00 heroku[web.1]: Process exited with status 1
2021-05-09T11:44:14.438297+00:00 heroku[web.1]: State changed from starting to crashed
2021-05-09T11:44:14.212635+00:00 app[web.1]:
2021-05-09T11:44:14.212651+00:00 app[web.1]: > CalculatorBot#1.0.0 start /app
2021-05-09T11:44:14.212652+00:00 app[web.1]: > index.js
2021-05-09T11:44:14.212652+00:00 app[web.1]:
2021-05-09T11:44:14.217415+00:00 app[web.1]: sh: 1: index.js: not found
2021-05-09T11:44:14.225315+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-05-09T11:44:14.225593+00:00 app[web.1]: npm ERR! syscall spawn
2021-05-09T11:44:14.225710+00:00 app[web.1]: npm ERR! file sh
2021-05-09T11:44:14.225853+00:00 app[web.1]: npm ERR! errno ENOENT
2021-05-09T11:44:14.229827+00:00 app[web.1]: npm ERR! CalculatorBot#1.0.0 start: `index.js`
2021-05-09T11:44:14.229941+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-05-09T11:44:14.230071+00:00 app[web.1]: npm ERR!
2021-05-09T11:44:14.230234+00:00 app[web.1]: npm ERR! Failed at the CalculatorBot#1.0.0 start script.
2021-05-09T11:44:14.230359+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-05-09T11:44:14.237148+00:00 app[web.1]:
2021-05-09T11:44:14.237336+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-05-09T11:44:14.237482+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-05-09T11_44_14_231Z-debug.log
And my package.json:
{
"name": "CalculatorBot",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start": "index.js"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"discord.js": "^12.5.3",
"math": "0.0.3"
}
}
Any ideas what I need to do to fix this, or if it is possible to run a Discord bot on Heroku?

change your package.json to the following
......
"start": "node index.js"
.......

Inside your Procfile put this line code same as I had listed here
web: node index.js
Now try again to deploy your WebApp with Heroku.

Related

Need help deploying full stack website to heroku: Error: There is likely additional logging output above

I'm pretty new to fullstack development and have been trying to upload my site on heroku, I get this error message and I'm guessing it has something to do with my package-lock.json file in the root folder.
I have both front end and back end folders under one parent folder.
Here is the link to the small project if you can check it out: https://github.com/manuelmort/tft-project
I usually upload some small sites to gh-pages but since they dont support server side code I have to use heroku. It builds succesfully but the site never starts because of the error message below on heroku CLI
2022-01-04T16:23:14.000000+00:00 app[api]: Build started by user manuelmort#gmail.com
2022-01-04T16:24:54.111750+00:00 app[api]: Deploy 8cc070c4 by user manuelmort#gmail.com
2022-01-04T16:24:54.111750+00:00 app[api]: Release v13 created by user manuelmort#gmail.com
2022-01-04T16:24:57.562224+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-04T16:25:02.000000+00:00 app[api]: Build succeeded
2022-01-04T16:25:04.610196+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-04T16:25:07.018112+00:00 app[web.1]:
2022-01-04T16:25:07.018129+00:00 app[web.1]: > tft-project#1.0.0 start /app
2022-01-04T16:25:07.018130+00:00 app[web.1]: > concurrently "npm run backend" "npm run client"
2022-01-04T16:25:07.018130+00:00 app[web.1]:
2022-01-04T16:25:07.022660+00:00 app[web.1]: sh: 1: concurrently: not found
2022-01-04T16:25:07.028749+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-04T16:25:07.028977+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-04T16:25:07.029095+00:00 app[web.1]: npm ERR! file sh
2022-01-04T16:25:07.029286+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-04T16:25:07.034404+00:00 app[web.1]: npm ERR! tft-project#1.0.0 start: `concurrently "npm run backend""npm run client"`
2022-01-04T16:25:07.034446+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-04T16:25:07.034492+00:00 app[web.1]: npm ERR!
2022-01-04T16:25:07.034537+00:00 app[web.1]: npm ERR! Failed at the tft-project#1.0.0 start script.
2022-01-04T16:25:07.034580+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likelyadditional logging output above.
2022-01-04T16:25:07.040214+00:00 app[web.1]:
2022-01-04T16:25:07.040320+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-04T16:25:07.040356+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-04T16_25_07_034Z-debug.log
2022-01-04T16:25:07.238236+00:00 heroku[web.1]: Process exited with status 1
2022-01-04T16:25:07.301484+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-04T16:25:07.307500+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-04T16:25:15.521992+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-04T16:25:17.284061+00:00 app[web.1]:
2022-01-04T16:25:17.284072+00:00 app[web.1]: > tft-project#1.0.0 start /app
2022-01-04T16:25:17.284073+00:00 app[web.1]: > concurrently "npm run backend" "npm run client"
2022-01-04T16:25:17.284073+00:00 app[web.1]:
2022-01-04T16:25:17.298996+00:00 app[web.1]: sh: 1: concurrently: not found
2022-01-04T16:25:17.316611+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-04T16:25:17.317012+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-04T16:25:17.317189+00:00 app[web.1]: npm ERR! file sh
2022-01-04T16:25:17.317369+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-04T16:25:17.337279+00:00 app[web.1]: npm ERR! tft-project#1.0.0 start: `concurrently "npm run backend""npm run client"`
2022-01-04T16:25:17.337583+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-04T16:25:17.337807+00:00 app[web.1]: npm ERR!
2022-01-04T16:25:17.337920+00:00 app[web.1]: npm ERR! Failed at the tft-project#1.0.0 start script.
2022-01-04T16:25:17.338041+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likelyadditional logging output above.
2022-01-04T16:25:17.347983+00:00 app[web.1]:
2022-01-04T16:25:17.350592+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-04T16:25:17.350682+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-04T16_25_17_338Z-debug.log
2022-01-04T16:25:17.534240+00:00 heroku[web.1]: Process exited with status 1
2022-01-04T16:25:17.755577+00:00 heroku[web.1]: State changed from starting to crashed
Any help would be much appreciated!
Turns out I needed to have concurrently under dependencies and not devDependecies branch in my package.json file,
I don't get the error anymore

Heroku failing node app - try to run nodemon instead of node

I'm deploying my node app to Heroku and it's trying to invoke it with nodemon rather than the node app.js I have defined. my package.json(partial) looks like:
"scripts": {
"start": "node app.js",
"test": "echo \"Error: no test specified\" && exit 1"
},
"engines": {
"node": "7.9.0"
},
when I run heroku logs I get
2018-02-22T22:41:44.798831+00:00 heroku[web.1]: Starting process with command `npm start`
2018-02-22T22:41:47.235623+00:00 app[web.1]:
2018-02-22T22:41:47.235654+00:00 app[web.1]: > api-barber-app#1.0.0 start /app
2018-02-22T22:41:47.235657+00:00 app[web.1]: > nodemon app.js
2018-02-22T22:41:47.235659+00:00 app[web.1]:
2018-02-22T22:41:47.247464+00:00 app[web.1]: sh: 1: nodemon: not found
2018-02-22T22:41:47.253052+00:00 app[web.1]: npm ERR! file sh
2018-02-22T22:41:47.253319+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-02-22T22:41:47.253543+00:00 app[web.1]: npm ERR! errno ENOENT
2018-02-22T22:41:47.253787+00:00 app[web.1]: npm ERR! syscall spawn
2018-02-22T22:41:47.254995+00:00 app[web.1]: npm ERR! api-barber-app#1.0.0 start: `nodemon app.js`
2018-02-22T22:41:47.255145+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-02-22T22:41:47.255420+00:00 app[web.1]: npm ERR!
2018-02-22T22:41:47.255617+00:00 app[web.1]: npm ERR! Failed at the api-barber-app#1.0.0 start script.
2018-02-22T22:41:47.255793+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-02-22T22:41:47.269400+00:00 app[web.1]:
2018-02-22T22:41:47.269715+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-02-22T22:41:47.269916+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-02-22T22_41_47_261Z-debug.log
2018-02-22T22:41:47.348415+00:00 heroku[web.1]: Process exited with status 1
2018-02-22T22:41:47.467170+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-22T22:41:47.475956+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-22T22:41:51.465439+00:00 heroku[web.1]: Starting process with command `npm start`
2018-02-22T22:41:54.918389+00:00 heroku[web.1]: Process exited with status 1
2018-02-22T22:41:54.679566+00:00 app[web.1]:
2018-02-22T22:41:54.679592+00:00 app[web.1]: > api-barber-app#1.0.0 start /app
2018-02-22T22:41:54.679594+00:00 app[web.1]: > nodemon app.js
2018-02-22T22:41:54.679596+00:00 app[web.1]:
2018-02-22T22:41:54.711632+00:00 app[web.1]: sh: 1: nodemon: not found
2018-02-22T22:41:54.759423+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-02-22T22:41:54.757722+00:00 app[web.1]: npm ERR! file sh
2018-02-22T22:41:54.761226+00:00 app[web.1]: npm ERR! syscall spawn
2018-02-22T22:41:54.760427+00:00 app[web.1]: npm ERR! errno ENOENT
2018-02-22T22:41:54.768513+00:00 app[web.1]: npm ERR! api-barber-app#1.0.0 start: `nodemon app.js`
2018-02-22T22:41:54.768637+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-02-22T22:41:54.768942+00:00 app[web.1]: npm ERR!
2018-02-22T22:41:54.769147+00:00 app[web.1]: npm ERR! Failed at the api-barber-app#1.0.0 start script.
2018-02-22T22:41:54.769369+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-02-22T22:41:54.825892+00:00 app[web.1]:
2018-02-22T22:41:54.826567+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-02-22T22:41:54.827196+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-02-22T22_41_54_816Z-debug.log
2018-02-22T22:41:54.934234+00:00 heroku[web.1]: State changed from starting to crashed
it try to run nodemon (what I had before) instead of node.js.
then when I push heroku it crash and not let me upload it right way.
heroku runs in a production environment by default so it does not install the dev dependencies, you can create a two npm script to avoid this error by running nodemon only in your localhost like that:
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start": "node app.js",
"start:dev": "nodemon --watch"
},
and when you want to run the project locally just run in your terminal npm run start:dev and it will load app.js by nodemon.
while in heroku npm start runs by default and load app.js from a normal node command and you get rid of that error.
I just had the same problem. After wasting a lot of time, I discovered that the whole time I was deploying the wrong branch. So if you are writing 'git push heroku master' for instance, 'master' is the branch you are pushing even if you are currently on a different branch.
Looks like nodemon is not in the dependencies, can you provide the package.json, make sure nodemon is in your dependencies

Heroku node.js app runs locally but crashes remotely

I have a node.js application which is not a web application.
Here's my package.json:
{
"name": "myapp-backend",
"version": "1.0.0",
"description": "MyApp PubNub backend",
"main": "app.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"repository": {
"type": "git",
"url": "https://git.heroku.com/myapp.git"
},
"keywords": [
"backend"
],
"author": "Pete Gu",
"license": "ISC",
"dependencies": {
"pubnub": "^4.3.3"
},
"engines": {
"node" : "6.9.2"
}
}
Contents of Procfile:
app: node app.js
It runs when I run heroku local. However, after pushing the code and checking logs with heroku logs I see this:
2016-12-22T06:07:01.276053+00:00 app[api]: Deploy fb193d3 by user xxxxx#xxxx.com
2016-12-22T06:07:01.477131+00:00 heroku[slug-compiler]: Slug compilation started
2016-12-22T06:07:01.477136+00:00 heroku[slug-compiler]: Slug compilation finished
2016-12-22T06:07:01.276053+00:00 app[api]: Release v13 created by user gpeetonn#gmail.com
2016-12-22T06:07:01.507095+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-22T06:07:02.759643+00:00 heroku[web.1]: Starting process with command `npm start`
2016-12-22T06:07:06.003266+00:00 heroku[web.1]: Process exited with status 1
2016-12-22T06:07:06.016232+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-22T06:07:06.017114+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-22T06:07:05.872484+00:00 app[web.1]: npm ERR! Linux 3.13.0-105-generic
2016-12-22T06:07:05.872909+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-12-22T06:07:05.873173+00:00 app[web.1]: npm ERR! node v6.9.2
2016-12-22T06:07:05.873421+00:00 app[web.1]: npm ERR! npm v3.10.9
2016-12-22T06:07:05.877486+00:00 app[web.1]: npm ERR! missing script: start
2016-12-22T06:07:05.875800+00:00 app[web.1]:
2016-12-22T06:07:05.877738+00:00 app[web.1]: npm ERR!
2016-12-22T06:07:05.877884+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-12-22T06:07:05.878031+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-12-22T06:07:05.892349+00:00 app[web.1]:
2016-12-22T06:07:05.892997+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-12-22T06:07:05.892655+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-12-22T06:07:07.532860+00:00 heroku[web.1]: Starting process with command `npm start`
2016-12-22T06:07:10.603753+00:00 app[web.1]: npm ERR! Linux 3.13.0-105-generic
2016-12-22T06:07:10.604065+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-12-22T06:07:10.604260+00:00 app[web.1]: npm ERR! node v6.9.2
2016-12-22T06:07:10.604476+00:00 app[web.1]: npm ERR! npm v3.10.9
2016-12-22T06:07:10.606525+00:00 app[web.1]:
2016-12-22T06:07:10.607621+00:00 app[web.1]: npm ERR! missing script: start
2016-12-22T06:07:10.607822+00:00 app[web.1]: npm ERR!
2016-12-22T06:07:10.607900+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-12-22T06:07:10.607998+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-12-22T06:07:10.618207+00:00 app[web.1]:
2016-12-22T06:07:10.618415+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-12-22T06:07:10.618645+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-12-22T06:07:10.718608+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-22T06:07:10.710362+00:00 heroku[web.1]: Process exited with status 1
...which completely doesn't make sense to me - why heroku tries to launch app using npm start instead of reading Procfile?
Heroku seems to be trying to start a web dyno, and doesn't seem to know about your Procfile.
Are you sure you added your Procfile to your git repo?
Anyway, try this:
heroku ps:scale web=0
heroku ps:scale app=1
You could also add "start": "node app.js" in the "scripts" section of your package.json.
I can see the error missing script: start So you need to add
"scripts": {
"start": "node bin/xxx" //your main file name
}
add this to your package.json.

Error while deploying NodeJs app on Heroku

I've tried to deploy my NodeJs app on Heroku, follows all steps on Heroku guide but I can't make it running. Here is the log:
2016-06-27T18:46:16.424477+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-27T18:46:18.594534+00:00 heroku[web.1]: Starting process with command `npm start`
2016-06-27T18:46:21.204182+00:00 app[web.1]: npm ERR! Linux 3.13.0-85-generic
2016-06-27T18:46:21.205909+00:00 app[web.1]: npm ERR! npm v3.8.6
2016-06-27T18:46:21.204971+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-06-27T18:46:21.209309+00:00 app[web.1]: npm ERR! missing script: start
2016-06-27T18:46:21.221679+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-27T18:46:21.209934+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-06-27T18:46:21.207755+00:00 app[web.1]:
2016-06-27T18:46:21.221362+00:00 app[web.1]:
2016-06-27T18:46:21.209552+00:00 app[web.1]: npm ERR!
2016-06-27T18:46:21.209740+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-06-27T18:46:21.221872+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-06-27T18:46:21.205374+00:00 app[web.1]: npm ERR! node v5.11.1
2016-06-27T18:46:22.240678+00:00 heroku[web.1]: Process exited with status 1
2016-06-27T18:46:22.255389+00:00 heroku[web.1]: State changed from starting to crashed
Any thoughts?
[EDIT]
package.json:
"engines": {
"node": "5.11.1",
"npm": "3.8.6"
},
"scripts": {
"start": "node app.js"
},
Procfile:
web: npm start
package.json
{
"name": "your-project-name",
"version": "1.0.0",
"description": "desc",
"main": "app.js",
"scripts": {
"start": "node app.js",
...
}
...
}
Procfile
Above package.json is file good to go without a Procfile. Yet, if you want to have one, you can define it as follows:
web: node app.js
You need to tell Heroku how to start your app. Either do that by specifying a "start" script in package.json, or by providing a Procfile.

Heroku Log "npm err"

I deployed an app to heroku, which worked, but when I go to the link, I get an application error. When I go to the heroku logs in my console, this is what I see:
2015-05-11T21:35:28.450778+00:00 app[web.1]: npm ERR!
2015-05-11T21:35:28.451031+00:00 app[web.1]: npm ERR! Failed at the showtrackr#0.0.0 start script 'node ./bin/www'.
2015-05-11T21:35:28.458702+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-05-11T21:35:28.451298+00:00 app[web.1]: npm ERR! This is most likely a problem with the showtrackr package,
2015-05-11T21:35:28.470607+00:00 app[web.1]:
2015-05-11T21:35:28.448240+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
2015-05-11T21:35:28.471022+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-05-11T21:35:28.458465+00:00 app[web.1]: npm ERR! not with npm itself.
2015-05-11T21:35:28.458841+00:00 app[web.1]: npm ERR! node ./bin/www
2015-05-11T21:35:28.471756+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-05-11T21:35:28.459009+00:00 app[web.1]: npm ERR! You can get their info via:
2015-05-11T21:35:28.459145+00:00 app[web.1]: npm ERR! npm owner ls showtrackr
2015-05-11T21:35:28.459299+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-05-11T21:35:29.488054+00:00 heroku[web.1]: State changed from starting to crashed
2015-05-11T21:35:29.489121+00:00 heroku[web.1]: State changed from crashed to starting
2015-05-11T21:35:29.467921+00:00 heroku[web.1]: Process exited with status 1
2015-05-11T21:35:33.804208+00:00 heroku[web.1]: Starting process with command `npm start`
2015-05-11T21:35:35.767544+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
2015-05-11T21:35:35.767452+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
2015-05-11T21:35:37.227415+00:00 app[web.1]: > node ./bin/www
If anyone can help with this, that would be awesome.
Don't know why but I ran
npm install
and repushed to heroku and everything worked.

Resources