Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
@uphold/http-errors
Advanced tools
This module provides a set of errors based on standard-http-error, reducing the boilerplate of adding error classes for the most common HTTP errors.
Install @uphold/http-errors with yarn:
$ yarn add @uphold/http-errors
Alternatively, with npm:
$ npm i @uphold/http-errors
The HttpError
serves as base error since all other errors extend it, use it to handle errors provided from this library.
const { BadRequestError, HttpError } = require('@uphold/http-errors');
try {
throw new BadRequestError();
} catch (e) {
console.log(e instanceof HttpError);
// true
}
Below is the list of all available errors:
Name | Code | Default message |
---|---|---|
AssertionFailedError | 500 | Internal Server Error |
BadRequestError | 400 | Bad Request |
ConflictError | 409 | Conflict |
ForbiddenError | 403 | Forbidden |
GoneError | 410 | Gone |
NotFoundError | 404 | Not Found |
ServiceUnavailableError | 503 | Service Unavailable |
TooManyRequestsError | 429 | Too Many Requests |
UnauthorizedError | 401 | Unauthorized |
ValidationFailedError | 400 | Validation Failed |
Import and throw an HTTP error:
const { ForbiddenError, UnauthorizedError } = require('@uphold/http-errors');
function authorize(user, permission) {
if (!user.role) {
throw new UnauthorizedError('User needs to authenticate');
}
if (permission === 'admin' && user.role !== 'admin') {
throw new ForbiddenError('Only admins allowed', { role: 'admin' })
}
return true;
}
All errors accept a message and a set of properties as arguments, or both:
const { BadRequestError } = require('@uphold/http-errors');
try {
throw new BadRequestError();
} catch (e) {
console.log(e);
// { BadRequestError: Bad Request
// at ...
// message: 'Bad Request', name: 'BadRequestError', code: 400 }
}
try {
throw new BadRequestError('foo');
} catch (e) {
// { BadRequestError: Bad Request
// at ...
// message: 'foo', name: 'BadRequestError', code: 400 }
}
try {
throw new BadRequestError({ foo: 'bar' });
} catch (e) {
console.log(e);
// { BadRequestError: Bad Request
// at ...
// message: 'Bad Request', foo: 'bar', name: 'BadRequestError', code: 400 }
}
try {
throw new BadRequestError('foo', { bar: 'biz' });
} catch (e) {
console.log(e);
// { BadRequestError: Bad Request
// at ...
// message: 'foo', bar: 'biz', name: 'BadRequestError', code: 400 }
}
Use the test
script to run the test suite:
$ yarn test
To test and check coverage use the cover
script:
$ yarn cover
A full coverage report will be generated on test/coverage folder.
Please create a PR with a description of the changes, its motivation and impacted areas, making sure the build passes.
$ yarn release [<version> | major | minor | patch]
MIT
FAQs
Set of errors based on http-standard-error
The npm package @uphold/http-errors receives a total of 4,554 weekly downloads. As such, @uphold/http-errors popularity was classified as popular.
We found that @uphold/http-errors demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 9 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
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.