Heroku deploys successful but application error

[megmatty]

Repo successfully deploys to Heroku but application gives error. Logs indicate that the server can't be started. Is there a way to configure package.json? Tried removing 'webpack-dev server' or replacing 'webpack dev-server' with webpack. Getting 'webpack not found' in Heroku logs.

[Gethyl]

Hi, there are couple of things to take care, though I have never deployed to Heroku, but I am guessing the following

• After you deploy you need to install all the packages from package.json
• Also you have to install mongoDb
• Noticed that on Heroku when you deploy and run npm install the packages are installed in production mode, so all the packages under devDependencies are not included. I am guessing this could be the reason why you get the error message related to webpack-dev-server/webpack not found.
• Also the ports are hardcoded as 3000/8080/27107 etc, which needs to be changed as process.env.PORT etc.

Since I have never deployed, I can only assume these as part of the solution.

[Tzikas]

I switched over the dependencies and
I changed
mongoose.connect('mongodb://localhost:27017/todos') to
mongoose.connect('mongodb://nikonikonikoniko:*******@ds155091.mlab.com:55091/yoooo')

var port = process.env.port || 3000; serve.listen(port,()=> {console.log("+++Gethyl Express Server with Socket Running!!!")})
and socket = io.connect("http://localhost:3000") to socket = io.connect()

and i"m getting this error in Heroku logs:

2017-05-31T21:07:52.328600+00:00 app[web.1]: Dropping unreachable code [(webpack)/hot/dev-server.js:62,0]
2017-05-31T21:07:52.328601+00:00 app[web.1]: Condition always true [./~/wtf-8/wtf-8.js:213,0]
2017-05-31T21:07:52.328602+00:00 app[web.1]: Declarations in unreachable code! [./~/wtf-8/wtf-8.js:224,0]
2017-05-31T21:07:52.328601+00:00 app[web.1]: Dropping unreachable code [./~/wtf-8/wtf-8.js:220,2]
2017-05-31T21:07:52.328602+00:00 app[web.1]: Declarations in unreachable code! [./~/wtf-8/wtf-8.js:226,0]
2017-05-31T21:07:52.328604+00:00 app[web.1]: Dropping unused variable object [./~/wtf-8/wtf-8.js:224,0]
2017-05-31T21:07:52.328603+00:00 app[web.1]: Side effects in initialization of unused variable freeModule [./~/wtf-8/wtf-8.js:8,0]
2017-05-31T21:07:52.328604+00:00 app[web.1]: Dropping unused variable hasOwnProperty [./~/wtf-8/wtf-8.js:225,0]
2017-05-31T21:07:52.328605+00:00 app[web.1]: Dropping unused variable key [./~/wtf-8/wtf-8.js:226,0]
2017-05-31T21:07:52.328605+00:00 app[web.1]: Dropping unused variable r [./~/socket.io-client/~/debug/browser.js:145,0]
2017-05-31T21:07:52.330312+00:00 app[web.1]: webpack: bundle is now VALID.
2017-05-31T21:08:24.504878+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2017-05-31T21:08:24.504878+00:00 heroku[web.1]: Stopping process with SIGKILL
2017-05-31T21:08:24.797556+00:00 heroku[web.1]: Process exited with status 137
2017-05-31T21:08:24.809234+00:00 heroku[web.1]: State changed from starting to crashed
2017-05-31T21:08:25.754995+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=morning-sierra-25621.herokuapp.com request_id=b509515f-7842-44e5-a46a-9b8f3643ec34 fwd="206.108.129.133" dyno= connect= service= status=503 bytes= protocol=https
2017-05-31T21:08:27.749670+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=morning-sierra-25621.herokuapp.com request_id=bda6b726-081a-4871-ae36-a661c6c0edb5 fwd="206.108.129.133" dyno= connect= service= status=503 bytes= protocol=https
2017-05-31T21:08:28.029030+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=morning-sierra-25621.herokuapp.com request_id=5ff99059-e6ed-41e3-bd6e-8f801a6d8531 fwd="206.108.129.133" dyno= connect= service= status=503 bytes= protocol=https

[Gethyl]

I have made couple of changes and was able to successfully deploy as you can see in the screenshot below.

You can look at the branch heroku-deploy to see the changes I have made.

But in general two observations:-

1. web dyno runs npm start, so I changed my start script to bring up the server and build using webpack
   "start": "webpack && npm run server"

2. I have added the below lines in server.js as I was getting 404 when I tried to open the web app. Adding the below lines resolved the issue.

const indexPath = path.join(__dirname, './index.html')
const distPath = express.static(path.join(__dirname, './dist'))

app.use('/dist', distPath)
app.get('/', function (req, res) { res.sendFile(indexPath) }) 

Also do note that this only brings up the webapp, but you will still need to work on how to bring up the mongodb and get that working with the app on Heroku. You can maybe explore on how to add additional dynos related to mongoDb I am guessing.

I am held up with few other things for couple of weeks so I may not be able to help you on that.

[ErikRobles]

In my case, I forgot to add the node and npm version in my package.json file.
"engine" : {
node: version-number,
npm: version-number
}