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.
httperrors
Advanced tools
Handy JavaScript Error classes representing the standard HTTP errors. Easily extensible and subclassable.
Exposes HTTP 4xx and 5xx status codes as JavaScript Error objects.
Make sure you have node.js and npm installed, then run:
npm install httperrors
var httpErrors = require('httperrors');
// Instantiate by name (UpperCamelCase):
var err = new httpErrors.NotFound('The thing you were looking for was not found');
console.warn(err.toString()); // NotFound [404]: The thing you were looking for was not found
if (identityCrisis) {
throw new httpErrors.ImATeapot('Dude...');
}
The error type is exposed as a true property on the instances, so your error handling code becomes quite readable (and you can avoid using instanceof):
if (err.NotFound) {
// ...
} else if (err.BadGateway) {
// ...
}
You can also create an error by status code (useful when proxying):
function fetchSomething(cb) {
var request = require('request');
request('http://example.com/thething', function (err, response) {
if (err) {
return cb(new (httpErrors[response.statusCode] || httpErrors.BadGateway)());
}
// ...
});
}
Creating your own Error classes:
var httpErrors = require('httperrors');
var MyError = httpErrors.createError({
type: 'MyError',
// Used when no message is handed to the constructor:
message: 'A slightly longer description of the error'
});
Instances can carry extra data about the error:
try {
throw new httpErrors.Forbidden({
message: "The message", // Not mandatory
data: {disallowedIds: [1, 3, 4, 6]}
});
} catch(e) {
console.warn(e.data); // {disallowedIds: [1, 3, 4, 6]}
}
Inheriting from an existing Error class:
var httpErrors = require('httperrors');
var NotFoundUnderTheBedError = httpErrors.createError({
type: 'NotFoundUnderTheBed',
message: 'I looked under the bed, but it was not found'
}, httpErrors.NotFound);
Instances of this error walk and quack like httpErrors.NotFound
instances, of course:
var ohDear = new NotFoundUnderTheBedError('No monsters today');
console.warn(ohDear.NotFound); // true
console.warn(ohDear.NotFoundUnderTheBed); // true
3-clause BSD license -- see the LICENSE
file for details.
FAQs
Handy JavaScript Error classes representing the standard HTTP errors. Easily extensible and subclassable.
The npm package httperrors receives a total of 60,667 weekly downloads. As such, httperrors popularity was classified as popular.
We found that httperrors demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.