Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
@jill64/attempt
Advanced tools
💠 Type safe error handling in one-line
npm i @jill64/attempt
Include error objects in the return value with a syntax similar to Lodash.attempt
.
Objects other than error instances are not captured.
import { attempt } from '@jill64/attempt'
// object | Error
const result = attempt(() => JSON.parse('Invalid JSON'))
Asynchronous functions can also be used.
Objects other than error instances are not captured.
Errors may be returned either synchronously or asynchronously.
See here for details.
import { attempt } from '@jill64/attempt'
// Promise<object> | Promise<Error> | Error
const result = attempt(async () => JSON.parse('Invalid JSON'))
Returns the object specified as the second argument when an error is caught.
Objects other than error instances are not captured.
import { attempt } from '@jill64/attempt'
// object | null
const result = attempt(() => JSON.parse('Invalid JSON'), null)
Executes the callback specified in the second argument when an error is caught.
The item filtered as an error instance is passed as the first argument of the callback.
import { attempt } from '@jill64/attempt'
// object | (string(error.message) | undefined)
const result = attempt(
() => JSON.parse('Invalid JSON'),
(error) => error?.message
)
The raw thrown object is passed as the second argument to the callback.
import { attempt } from '@jill64/attempt'
// object | 'Syntax Error' | null
const result = attempt(
() => JSON.parse('Invalid JSON'),
(error, projectile) => {
if (error instanceof SyntaxError) {
return 'Syntax Error'
}
console.error('Unknown Object', projectile)
return null
}
)
Promise<Error>
when specified?Asynchronous function to Reject
// () => Promise<object>
const func = async () => {
try {
JSON.parse('Invalid JSON')
} catch {
throw new Error('Error')
}
}
// Assign `null` by catch reject
const result = func().catch(() => null)
// `null`
return result
Asynchronous function that throws an error immediately (does not Reject)
// () => Promise<object>
const func = () => {
try {
const obj = JSON.parse('Invalid JSON')
return new Promise(
(resolve) => resolve(obj),
(reject) => reject('Reject')
)
} catch {
throw new Error('Error')
}
}
// Error: Not Reject Error (Can't catch)
const result = func().catch(() => null)
return result
Although this is catchable in JavaScript syntax, it is actually thrown synchronously and cannot be caught.
Also, there is no way to check if a Promise
is returned before the function is executed.
Therefore, the error return value of an asynchronous function is always Error | Promise<Error>
.
FAQs
💠 Type safe error handling in one-line
We found that @jill64/attempt 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.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.