
Product
Introducing Reachability for PHP
Reachability analysis for PHP is now available in experimental, helping teams identify which vulnerabilities are actually exploitable.
safe-errors
Advanced tools
In my opinion its simpler to handle errors just like I handle everything else. Normally, errors are handled on a separate codepath. This module helps normalize the codepath for the return values (including errors) from asynchronous functions.
In my opinion its simpler to handle errors just like I handle everything else. Normally, errors are handled on a separate codepath. This module helps normalize the codepath for the return values (including errors) from asynchronous functions.
npm i --save safe-errors
let user
try {
user = await getUser('http://www.example.com/api/v1/users/123')
} catch (e) {
log(e)
// handle error in some way
}
user.name = 'New Name'
let postResponse
try {
postResponse = await saveUser('http://www.example.com/api/v1/users/123')
} catch (e) {
log(e)
// handle error in some way
}
const { safep } = require('safe-errors')
let getResult = await safep(getUser)('http://www.example.com/api/v1/users/123')
if (getResult.success === false) {
log(getResult.error)
// handle error in some way
}
let user = getResult.payload
user.name = 'New Name'
let saveResult = await safep(saveUser)('http://www.example.com/api/v1/users/123', user)
if (saveResult.success === false) {
log(saveResult.error)
// handle error in some way
}
const { pipeP, merge } = require('ramda')
const { safep } = require('safe-errors')
const getUserP = () => safep(getUser)('http://www.example.com/api/v1/users/123')
const updateUser = (user) => {
return merge(user, {
name: 'New name'
})
}
const saveUserP = (user) => safep(saveUser)('http://www.example.com/api/v1/users/123', user)
const handleError = (result) => {
if (result.success === false) {
log(result.success === false)
// maybe return a default
return {}
}
return result.payload
}
// Easier to pipe when errors are predictable
let updateAndSaveUser = pipeP(getUserP, handleError, updateUser, saveUser, handleError)
let updateResult = await updateAndSaveUser()
if (updateResult.success === false) {
log(updateResult.error)
}
const { readFile } = require('fs')
fs.readFile('file.txt', (err, data) => {
if (err) {
log(err)
// handle error in some way
}
console.log(data)
})
const { readFile } = require('fs')
const { safecb } = require('safe-errors')
let result = await safecb(readFile)('file.txt')
if (result.error) {
log(result.error)
// handle error in some way
}
console.log(result.payload) // contents of file
console.log(result.args) // array of arguments passed into done callback
FAQs
In my opinion its simpler to handle errors just like I handle everything else. Normally, errors are handled on a separate codepath. This module helps normalize the codepath for the return values (including errors) from asynchronous functions.
We found that safe-errors 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.

Product
Reachability analysis for PHP is now available in experimental, helping teams identify which vulnerabilities are actually exploitable.

Product
Export Socket alert data to your own cloud storage in JSON, CSV, or Parquet, with flexible snapshot or incremental delivery.

Research
/Security News
Bitwarden CLI 2026.4.0 was compromised in the Checkmarx supply chain campaign after attackers abused a GitHub Action in Bitwarden’s CI/CD pipeline.