Release v1.2.1 — Smarter Error Handling & Cleaner Logs

🚀 Overview

This release improves the developer experience by preventing unnecessary or misleading error logs and refining how Express errors are handled internally.

♻️ Fixes & Improvements

• 🛠️ Ignored Favicon Requests:
  Added logic to silently handle /favicon.ico requests, preventing false 404 error logs when browsers automatically request a favicon (especially common when reusing port 3000 after a frontend app).

• 🧩 TypeScript Compatibility Fix:
  Improved middleware typing using ErrorRequestHandler for smoother integration in TypeScript projects.

• 🧼 Cleaner Console Output:
  Enhanced log clarity — no more noisy or irrelevant errors from harmless browser behavior.

💡 Notes

If you were seeing a Cannot GET /favicon.ico error when switching from a Next.js or React app to an Express server on the same port, upgrading to this version will automatically resolve it.

1.2.0 – Removed http-status-codes Re-export

This update removes the http-status-toolkit re-export from express-error-toolkit.
The package is now more lightweight and keeps its focus solely on error handling.

If your project was using:

import { StatusCodes } from 'express-error-toolkit';

Please update it to:

import { StatusCodes } from 'http-status-toolkit';

📦 Install:

npm install http-status-toolkit

v1.1.2 — Customizable Intro Line for Enhanced DX

✨ What's New

• Added introLine support for custom or toggleable intro messages in console logs.

Users can now:

 - Disable the intro line by setting introLine: false

 - Customize it with their own message: introLine: 'Your custom intro'

• Default intro line: 💥 Even the best code breaks sometimes! Let's debug...

🛠️ Example

setErrorOptions({
  introLine: false
});

// or

setErrorOptions({
  introLine: '🚨 Whoops! An error occurred'
});

v1.1.1 – Add status code logging to console

Added styled status code output in the console alongside error messages and stack traces, improving developer visibility and debugging speed.

v1.1.0 – Configurable Logging & Stack Trace + Developer-Friendly Console Output

📝 Release Description
This version adds more flexibility and polish to error handling in Express.js apps.

✨ What’s New:
✅ showStack and logError are now enabled by default, but automatically disabled in production.

✅ Customize behavior using .env (SHOW_STACK, LOG_ERROR) or programmatically via setErrorOptions().

✅ Console logs are now color-coded with ANSI styling for better readability.

🖼️ Included a screenshot in the README to demonstrate improved console output.

This release improves developer experience while giving you full control over error logging behavior.

v1.0.1 - Optional Stack Trace and Logging Support

Added support to optionally hide stack traces and disable error logging in globalErrorHandler.

You can now configure via .env:

SHOW_STACK=false
LOG_ERROR=false

Or programmatically in the code:

setToolkitOptions({
showStack: false,
logError: false
});

v1.0.0 - First stable release

🎉 First stable release of express-error-toolkit!

✅ Custom error classes (e.g., BadRequestError, NotFoundError)
✅ Async error handler wrapper
✅ Global & Not Found middleware
✅ Built-in support for http-status-toolkit
✅ Type-safe & DX-focused design

Beta v0.1.0

Initial Release