Check if an HTTP status code is an error code
Check error code from axios error response
Error constructor for test and validation frameworks that implements standardized AssertionError specification.
Error comparison and information related utility for node and the browser
An iteration of the Node.js core streams with a series of improvements
Check if a value is a Fetch network error
No description provided.
ECMAScript parser
Check whether a request can be retried based on the `error.code`
Type check values
richer JavaScript errors
just emit 'log' events on the process object
A ridiculously light-weight argument validator (now browser friendly)
Node.js final http responder
An overlay for displaying stack frames.
EventEmitter3 focuses on performance while maintaining a Node.js AND browser compatible interface.
A library to make errors.
Throw, identify, and decode Solana JavaScript errors
Standard error objects for pug
Run an array of functions in parallel
Core functions & classes shared by multiple AWS SDK clients.
`Start a promise chain
Write files in an atomic fashion w/configurable ownership
A simple Node.js module to check if a TCP port is already bound.
The WindowsError gem provides an easily accessible reference for standard Windows API Error Codes. It allows you to do comparisons as well as direct lookups of error codes to translate the numerical value returned by the API, into a meaningful and human readable message.
The gem enhances Exception#message by adding a short explanation where the exception is raised
Registry to register errors with unique codes and more.
Return HTTP error codes while rendering the corresponding error page in Rails.
ErrorsFullDetails extends ActiveModel::Errors to allow adding error codes to error messages
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
A linter for checking errors in javascript code
A simple scraper to pull Facebook's list of error codes and descriptions from the documentation.
Simple way to maintain custom error codes and there messages with I18n.
"sinatra-errorcodes is the sinatra extension that contains a pack of HTTP error status code and message"
cuts off most of the file path and prints out the backtrace line by line for easier parsing. Except for native code errors (ie Syntax, method undefined).
Provides a convenience method to retry blocks of code that might fail due to temporary errors, e.g. a network service that becomes temporarily unavailable. The retries are timed to back-off exponentially (2^n seconds), hopefully giving time for the remote server to recover.