![38% of CISOs Fear They’re Not Moving Fast Enough on AI](https://cdn.sanity.io/images/cgdhsj6q/production/faa0bc28df98f791e11263f8239b34207f84b86f-1024x1024.webp?w=400&fit=max&auto=format)
Security News
38% of CISOs Fear They’re Not Moving Fast Enough on AI
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
@dotcom-reliability-kit/serialize-error
Advanced tools
A utility function to serialize an error object in a way that's friendly to loggers, view engines, and converting to JSON
A utility function to serialize an error object in a way that's friendly to loggers, view engines, and converting to JSON. This module is part of FT.com Reliability Kit.
Install @dotcom-reliability-kit/serialize-error
as a dependency:
npm install --save @dotcom-reliability-kit/serialize-error
Include in your code:
import serializeError from '@dotcom-reliability-kit/serialize-error';
// or
const serializeError = require('@dotcom-reliability-kit/serialize-error');
serializeError
The serializeError
function accepts an error-like object (e.g. an instance of Error
or an object with a message
property) and returns a plain JavaScript object (conforming to the SerializedError
type) which contains the relevant properties:
serializeError(new Error('example message'));
// {
// name: 'Error',
// code: 'UNKNOWN',
// message: 'An error occurred',
// isOperational: false,
// relatesToSystems: [],
// stack: '...',
// statusCode: null,
// data: {}
// }
You can also pass in a plain object if you already have one that looks like an error (e.g. from a JSON API response):
serializeError({
message: 'example message'
});
SerializedError
typeThe SerializedError
type documents the return value of the serializeError
function. It will always have the following properties, extracting them from a given error object.
SerializedError.name
This is extracted from the error.name
property and is always cast to a String
. It defaults to "Error"
.
SerializedError.code
This is extracted from the error.code
property and is always cast to a String
. It defaults to "UNKNOWN"
.
SerializedError.message
This is extracted from the error.message
property and is always cast to a String
. It defaults to "An error occurred"
, which is not very helpful but we want this library to be resilient to unexpected input data.
SerializedError.isOperational
This indicates whether the error is operational (known about). See the documentation for OperationalError
for more information. It is extracted from the error.isOperational
property. It is always cast to a Boolean
and defaults to false
.
SerializedError.relatesToSystems
This array contains a list of system codes which are related to the error. It defaults to an empty array.
SerializedError.stack
This is extracted from the error.stack
property. If this property is not a string, then it will default to null
.
SerializedError.statusCode
This is extracted from the error.statusCode
property first, then the error.status
property otherwise (we use look at both properties to maintain compatibility with third-party request and error libraries). These are always cast to a Number
and this property defaults to null
.
SerializedError.data
This is extracted from the error.data
property. If this property is not a plain object, then it will default to an empty object: {}
.
See the central contributing guide for Reliability Kit.
Licensed under the MIT license.
Copyright © 2022, The Financial Times Ltd.
FAQs
A utility function to serialize an error object in a way that's friendly to loggers, view engines, and converting to JSON
The npm package @dotcom-reliability-kit/serialize-error receives a total of 5,186 weekly downloads. As such, @dotcom-reliability-kit/serialize-error popularity was classified as popular.
We found that @dotcom-reliability-kit/serialize-error demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.