Problematic error handler

[FarahZaqout]

posts-project/src/app.js

Line 28 in 543acb9

app.use((err, req, res, next) => {

If that error ever gets thrown in production i will have no way of knowing what went wrong.

you need to log your errors somewhere, you can stringify an error object and store it in database, or in a txt file which is really a bad way of doing it.

for now just add a console.log(err) so you can at least reproduce the issue and see the error, but in serious production projects you will probably need to log the error somewhere.

I prefer to stringify the following object and put it somewhere

{
 date: new Date(),
 error: err.stack,
 url: req.url
 ip: req.ip // if your project does stuff based on region this might be useful, but usually is not 
 really necessary
}

[NouraldinS]

@FarahZaqout Absolutely disagreeing, YES he should be more descriptive about the messages he is sending to the front end, but absolutely never send your err.stack to your client. That is basically you're calling kids to try and hack you. The error description should be just enough to tell the user a useful message about how to fix it if possible.

[FarahZaqout]

@NoureldeanSaed I probably wasn't clear in what I wrote, but I am not talking about sending the error to the client.

I'm talking about logging his errors somewhere for his own use. If a server crashes, it's useful to know what happened and when, which route as well. It helps a lot with the debugging.

This object will not go to the client, but some place for the developers who maintain the app.