error-manager-helper
v3.24.0
Published
Express error middleware manager
Downloads
953
Readme
𝑬𝒓𝒓𝒐𝒓𝑴𝒂𝒏𝒂𝒈𝒆𝒓 🌟💻
- Express error middleware with custom error types for easy error handling for different use cases.
Init
- If you are not using express then you can still use the custom error types. But then they will only throw the error and it will not be sended to the client!
import axios, { AxiosError } from 'axios'
import express from 'express'
import 'express-async-errors'
import { errorMiddleware, HttpClientError } from 'error-manager-helper'
const app = express()
// Sample route to trigger custom error HttpClientError with axios
app.get('/httpclient-error', async() => {
try {
await axios.get('https://anySample.website/notFound')
} catch (err) {
throw new HttpClientError('Test error', err as AxiosError)
}
})
// Include error middleware
app.use(errorMiddleware)
const port = 3000
const server = app.listen(port)
console.log(`Server is running on port ${port}`)
Response:
const res = await axios.get('http://localhost:3000/httpclient-error')
console.log(res.response.data)
{
name: "HttpClientError",
environment: "npx",
timestamp: "2024-09-22T17:07:27.603Z",
message: "Test error",
httpStatus: 404,
data: {
url: "https://anySample.website/notFound",
method: "get",
responseData: "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>Cannot GET /notFound</pre>\n</body>\n</html>\n",
headers: {
Accept: "application/json, text/plain, */*",
"User-Agent": "axios/1.7.7",
"Accept-Encoding": "gzip, compress, deflate, br",
},
errorMessage: "Request failed with status code 404",
},
stack: "HttpClientError: Test error\n at /home/username/Projects/ErrorManager/test/integration/pretestAll.ts:56:13\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
error: {
// Original axios error will be here..
}
}
𝐸𝓇𝓇𝑜𝓇𝓈 🌟💻
𝑩𝒂𝒔𝒆𝑬𝒓𝒓𝒐𝒓 🚨
Response HTTP Status 500
Arguments:
- 1: {string} - Error Message
- 2: {Error} [optional] - Error
import { BaseError } from 'error-manager-helper'
try {
const chatCompletion = await this.client.chat.completions.create(params)
return chatCompletion
} catch (err: unknown) {
throw new BaseError('Can not create chat completion', err as Error)
}
𝐇𝐭𝐭𝐩𝐂𝐥𝐢𝐞𝐧𝐭𝐄𝐫𝐫𝐨𝐫 🌐
Will be the status of the error of your HTTP request
Supported HTTP clients:
- axios
Arguments:
- 1: {string} - Error Message
- 2: {AxiosError} - Axios Error
import axios, { type AxiosError } from 'axios'
import { HttpClientError } from 'error-manager-helper'
try {
const response = await axios.request(config)
return response
} catch (err: unknown) {
throw new HttpClientError('Can not send request', err as AxiosError)
}
𝑽𝒂𝒍𝒊𝒅𝒂𝒕𝒊𝒐𝒏𝑬𝒓𝒓𝒐𝒓 ❌
Response HTTP Status 400
Arguments:
- 1: {string} - Error Message
- 2: {object} - Data that is not valid.
- 3: {Error} [optional] - Error
import { ValidationError } from 'error-manager-helper'
if (test !== 'expectedValue') {
throw new ValidationError('test ist not valid', { test })
}
𝑹𝒆𝒔𝒐𝒖𝒓𝒄𝒆𝑵𝒐𝒕𝑭𝒐𝒖𝒏𝒅𝑬𝒓𝒓𝒐𝒓 🔍
Response HTTP Status 404
Arguments:
- 1: {string} - Error Message
- 2: {object} - Data that is not valid.
- 3: {Error} [optional] - Error
import { ResourceNotFoundError } from 'error-manager-helper'
const doc = await Model.findOne({ storeId })
if (!doc) {
throw new ResourceNotFoundError('doc not found', { storeId })
}
𝑹𝒖𝒏𝑻𝒊𝒎𝒆𝑬𝒓𝒓𝒐𝒓 ⏳
Response custom defined HTTP status
Arguments:
- 1: {string} - Error Message
- 2: {StatusCodes} - HTTP status code [Default 500]
- 3: {Error} [optional] - Error
import { RuntimeError, StatusCodes } from 'error-manager-helper'
const res = getKey()
if (res.status === 403) {
throw new RuntimeError('Request is forbidden', StatusCodes.FORBIDDEN)
}
npm_lifecycle_event 🔧🛠️
- Some errors may leak sensitive informations in the stack, the message itself or by the additional provided data which you include to your custom error.
- For this reason when you use
npm_lifecycle_event=start
your providederror, data and stack trace will be sanitized
and not sended to the client. Sample response:
- For this reason when you use
{
"name": "ValidationError"
"environment": "start",
"timestamp": "2024-09-22T17:02:07.987Z"
"message": "Collection name 'test!' can not contain special characters",
"httpStatus": 400,
"error": '[SANITIZED]',
"data": '[SANITIZED]',
"stack": '[SANITIZED]'
}
- With all other npm_lifecycle_event it will be not sanitized. However, even with npm_lifecycle_event=start the full error will logged with console.error.
Tests ✅
Interfaces
- BaseErrorInterface
- HttpClientErrorInterface
- ResourceNotFoundErrorInterface
- RuntimeErrorInterface
- ValidationErrorInterface
Integration Test
- The example below demonstrates an integration test for an internal service that throws a
BaseError
.
import { it, expect, expectTypeOf } from 'vitest'
import { type BaseErrorInterface, StatusCodes } from 'error-manager-helper'
it('should return 500 with BaseError details - error passed', async() => {
try {
await axios.get('https://localhost:3000/base-error?param=wrong')
throw new Error('Base Error Test - This line should not be called')
} catch (e: unknown) {
const { response } = e as AxiosError
expect(response?.status).to.equal(StatusCodes.INTERNAL_SERVER_ERROR)
const data = response?.data as BaseErrorInterface
expectTypeOf(data).toEqualTypeOf<BaseErrorInterface>()
expect(data.error).toEqual(`Error: ${errorMessageFromService}`)
expect(data.message).toBe(errorMessage)
}
})
Unit Test
import { it, expect, expectTypeOf } from 'vitest'
import { BaseError, type BaseErrorInterface } from 'error-manager-helper'
describe('Any test block', () => {
const errMsg = 'Test error'
const errMsgOriginal 'Test error original'
const error = new Error(errMsgOriginal)
const fn = () => {
throw new BaseError(errMsg)
}
it('should throw BaseError', () => {
try {
fn()
throw new Error('Base Error Test - This line should not be called')
} catch (err: unknown) {
const typedErr = err as BaseErrorInterface
expectTypeOf(typedErr).toEqualTypeOf<BaseErrorInterface>()
expect(typedErr).toBeInstanceOf(BaseError)
expect(typedErr.error).toEqual(error)
expect(typedErr.message).toBe(errMsg)
}
})
})