Package Exports
- feathers-errors
- feathers-errors/handler
- feathers-errors/not-found
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (feathers-errors) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
feathers-errors
Common error types for feathers apps
Getting Started
Feathers errors come with feathers by default. So typically you don't need to install it at all.
In the event that you do need to install it:
npm install --save feathers-errorsDocumentation
Current Error Types:
BadRequest: 400NotAuthenticated: 401PaymentError: 402Forbidden: 403NotFound: 404MethodNotAllowed: 405NotAcceptable: 406Timeout: 408Conflict: 409LengthRequired: 411Unprocessable: 422TooManyRequests: 429GeneralError: 500NotImplemented: 501BadGateway: 502Unavailable: 503
Pro Tip: Feathers service adapters (ie. mongodb, memory, etc.) already emit the appropriate errors for you. :-)
Usage:
import errors from 'feathers-errors';
// If you were to create an error yourself.
var notFound = new errors.NotFound('User does not exist');
// You can wrap existing errors
var existing = new errors.GeneralError(new Error('I exist'));
// You can also pass additional data
var data = new errors.BadRequest('Invalid email', {email: 'sergey@google.com'});
// You can also pass additional data
var dataWithoutMessage = new errors.BadRequest({email: 'sergey@google.com'});
// If you need to pass multiple errors
var validationErrors = new errors.BadRequest('Invalid Parameters', {errors: {email: 'Email already taken'} });
// You can also omit the error message and we'll put in a default one for you
var validationErrors = new errors.BadRequest({errors: {email: 'Invalid Email'} });License
Copyright (c) 2016 Feathers Contributors
Licensed under the MIT license.

