
Research
/Security News
npm Author Qix Compromised via Phishing Email in Major Supply Chain Attack
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.
@mulesoft/request-error-handler
Advanced tools
Standardized error handler for rendering API responses with i18n
Standardized error handler for rendering API responses with i18n. Automatically renders with support for JSON, XML, HTML and plain text.
npm install request-error-handler --save
For the error handler to work, you must emit an error with an array of requestErrors. The format for requestErrors is defined below as an array of RequestErrors.
var errorHandler = require('request-error-handler')
var express = require('express')
var app = module.exports = express()
function responder (req, res, error, stack) { /* Custom respond logic here */ }
var defaultLanguage = 'en'
var customMessages = {}
app.use(errorHandler(responder, defaultLanguage, customMessages))
Options
responder Provide a custom error formatter with optional stack depending on environment (default: errorHandler.responder)defaultLanguage Override the default i18n language of English (default: en)customMessages Merge custom i18n messages with default messages (default: {}, see interface below)The messages interface is as follows:
interface CustomMessages {
[type: string]: {
[keyword: string]: {
[language: string]: (error: RequestError) => string
}
}
}
The only restriction on errors that can be formatted using request-error-handler is that the error instance has an array of error objects on the requestErrors property. Every error object MUST follow the following interface:
interface RequestError {
type: 'json' | 'form' | 'headers' | 'query' | 'xml' | string /* Comes with standard types built-in, but you can also provide your own */
keyword: string /* Keyword that failed validation */
message: string /* Merged with i18n when available */
id?: string /* A unique identifier for the instance of this error */
dataPath?: string /* Natural path to the error message (E.g. JSON Pointers when using JSON) */
data?: any /* The data that failed validation */
schema?: any /* The schema value that failed validation */
detail?: string /* Additional details about this specific error instance */
meta?: { [name: string]: string } /* Meta data from the error (XML validation provides a code, column, etc.) */
}
To automatically create a compatible error instance, use errorHandler.createError and pass an array of errors with an option status number.
Apache License 2.0
FAQs
Standardized error handler for rendering API responses with i18n
The npm package @mulesoft/request-error-handler receives a total of 0 weekly downloads. As such, @mulesoft/request-error-handler popularity was classified as not popular.
We found that @mulesoft/request-error-handler demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.

Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.

Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.