hagopj13 / hagopj13/node-express-boilerplate
use express-async-errors instead of catchAsync
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
```
const express = require('express');
require('express-async-errors');
const User = require('./models/user');
const app = express();
app.get('/users', async (req, res) => {
const users = await User.findAll();
res.send(users);
});
```
Contributor guide
Research direction
Start by locating the project's catchAsync helper and the Express application setup, then compare how async route handlers are currently registered with the express-async-errors usage shown in the issue. Done means the intended handlers use express-async-errors instead of catchAsync without changing their behavior; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, node.js
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100