jsend VS node-express-boilerplate

For each endpoint you call, it’s probable for you to encounter an error response, especially if your dealing with authenticated-based fetch calls. In that scenario, you will want to make sure you have a dedicated error handler that deals with this, taking into account of the expected error JSON response schema. In our hypothetical example, our api service uses the JSend JSON response schema.

Hi, I'm trying to make a call to a service I created which returns a JSON response in the JSend format, however I'm really struggling to marshal the response into a normal struct. The payload always seems to be marshaled into a map rather than properly into the struct fields.

We have used Jsend to format our API response. This is it for this blog. I hope you enjoyed it. If you have any questions, feel free to email it :), I am not joking I don't have a comment section on my blog yet.

However, I'm creating my own API and I see some recommendations such as jsend which recommends your API to use a data key to separate metadata from the specific requested data.

A better approach would be to enforce one of several JSON schema's like JSON:API or Jsend.

I liked your catchAsync function so I don't have to use try-catch in every other function inside the controller. Also, I like how you manage the errors, but I need to modify your class to show all messages with the JSend convention.

Try boilerplate https://github.com/hagopj13/node-express-boilerplate

Here’s a pretty good example of a production API built with Express. https://github.com/hagopj13/node-express-boilerplate

The Express Boiler Plate Project Sets it to true

This repo has a decent starter project with a good middleware setup and a decent way of structuring the project, but no typescript.