spudly / error-wrapper Goto Github PK

💣 A base class for creating custom JavaScript error classes that wrap around a child error object.

License: MIT License

JavaScript 100.00%

stack-traces caused-by error exception class javascript subclass npm-package

error-wrapper's Introduction

ErrorWrapper

A Base Class for creating error objects that wrap around other error objects without trashing the stack trace of the original error. Stack traces will appear in the following format:

ERROR MyCustomErrorWrapper Some Error Message
  at /path/to/some/js/file.js:123:456
  at /path/to/some/other/js/file.js:123:456
...
Caused By: Error: Some Other Error Message
  at /path/to/some/js/file.js:123:456
  at /path/to/some/other/js/file.js:123:456

All the Badges...

Usage

import ErrorWrapper from 'error-wrapper';

class MyErrorWrapper extends ErrorWrapper {

  // Add extra properties/methods if desired:

  get code() {
    return 'MYERRORWRAPPER';
  }

}

// later...
throw new MyErrorWrapper('error message', originalError);

License

MIT

error-wrapper's People

Contributors

Stargazers

Watchers

error-wrapper's Issues

An in-range update of browserify is breaking the build 🚨

Version 14.2.0 of browserify just got published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	14.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 5 commits .

18e1d65 14.2.0
0e1a7a0 add cli support for --transform-key to support mode's like production/staging/etc..
a5aa660 Merge pull request #1701 from wogsland/doc-fix
ae281bc Fixed documentation formatting that was bugging me
fe8c57b async test for node 7

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

Version 0.13.3 of husky just got published.

Branch	Build failing 🚨
Dependency	husky
Current Version	0.13.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As husky is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 9 commits .

4b5011e 0.13.3
6b92bb8 Comments
c6f8bb1 0.13.3-0
a2da709 Prefer nvm over Node global install
652c7f0 Update README.md
d05a7b3 Update README.md
0bb5798 Fix tests
7af95d3 update failure message (#107)
be435ca Update CHANGELOG.md

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of prettier is breaking the build 🚨

The devDependency prettier was updated from `1.16.1` to `1.16.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 1.16.2

🔗 Changelog

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

spudly / error-wrapper Goto Github PK

error-wrapper's Introduction

ErrorWrapper

All the Badges...

Usage

License

error-wrapper's People

Contributors

Stargazers

Watchers

error-wrapper's Issues

Version 14.2.0 of browserify just got published.

Version 0.13.3 of husky just got published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

The devDependency prettier was updated from 1.16.1 to 1.16.2.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency prettier was updated from `1.16.1` to `1.16.2`.