Package Exports

generaterr

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 (generaterr) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Generaterr

Generates custom and valid node.js error functions for node.js.

Installation

npm install generaterr --save

Usage

Basis Usage

var ParseError = generaterr('ParseError');

try
{
  throw new ParseError('Could not parse file due to missing semicolons');
} catch(e) {
  console.log(e.message);
  console.log(e.name);
  console.log(e.stack);
}

Formatting messages

var ParseError = generaterr('ParseError');

try
{
  throw new ParseError('Could not parse file "%s" due to missing semicolons at line %d:%d', 'input.js', 10, 12);
} catch(e) {
  // Message: 'Could not parse file "input.js" due to missing semicolons at line 10:12'
}

Generator Arguments

var NotFoundError = generaterr('NotFoundError', { status : 404 });

var notFoundError = new NotFoundError('Could find resource /api/random/numbers');

console.log(notFoundError.status);

// Prints '404'

Constructor Arguments

var ParseError = generaterr('ParseError');

var err = new ParseError('Could not parse file "%s" due to missing semicolons at line %d:%d', 'input.js', 10, 12, { status : 'FATAL' });

console.log(err.message)
// Prints 'Could not parse file "input.js" due to missing semicolons at line 10:12'

console.log(err.status)
// Prints 'FATAL'

Options

captureStackTrace, defaults to 'true'

Turning off stack trace generation may be useful for business logic exceptions that do not require a stack trace.

var ParseError = generaterr('ParseError', null, { captureStackTrace : false });