npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

extended-exceptions

v2.1.0

Published

Easy custom js exceptions for node & browser, AMD.

Downloads

27

Readme

extended-exceptions.js

Build Status NPM version Bower version Dependency Status Project status license graph status Code Climate Total views Gittip

Introduction

Allow easy declaration of custom javascript errors/exceptions.

Also provides common exceptions for Javascript that are missing in the standard : RuntimeError, NotImplementedError, InvalidArgument, OutOfRange, etc. (inspiration taken from the C++11 standard)

Works in node.js + browser, AMD.

Full testsuite. No dependencies.

Includes special workarounds for Firefox "Error" object which has sometimes a strange behaviour.

License : public domain (http://unlicense.org/)

Interesting reads :

  • http://dailyjs.com/2014/01/30/exception-error/
  • http://en.cppreference.com/w/cpp/error/exception

Predefined errors

Note : we keep the "error" naming scheme of standard javascript.

Error (standard)  <-- javascript root exception
+ EvalError       <-- Vanilla javascript exceptions
+ RangeError      <-- ...
+ ReferenceError  <-- ...
+ SyntaxError     <-- ...
+ TypeError       <-- ...
+ URIError        <-- ...
+ ExtendedError   <-- Here start our custom exceptions
  + LogicError
    + InvalidArgument
    + LengthError
    + OutOfRange
    + InvariantNotMet
  + RuntimeError
    + NotImplemented
    + UnknownEnumValue
    + IllegalState

Usage

if (typeof define !== 'function') { var define = require('amdefine')(module); } // node only

define(
[
	'extended-exceptions'
],
function(EE) {
	"use strict";

	// Feature 1 - use one of the predefined errors
	throw new EE.NotImplemented("TODO !");
	throw new EE.InvalidArgument("Please !");

Defining our own exceptions inheriting from an existing one :

define(
[
	'extended-exceptions'
],
function(EE) {
	"use strict";

	// Feature 2 - create a brand new error
	// inheriting from (for example) RuntimeError (could be just Error)
	var CustomJsonSerializationError = EE.create_custom_error("CustomError", EE.RuntimeError);

	// Alternative 1 - use it directly
	throw new CustomJsonSerializationError("Oups !");

	// Alternative 2 - use it to cast an existing error
	try {
		JSON.parse(stuff);
	}
	catch(e) {
		throw new CustomJsonSerializationError(e); // new error will have same stack and message
	}

	...
	
	console.log( caught_error.name );
	console.log( caught_error.message );
	console.log( caught_error.stack );

Catching and testing exceptions :

  • exactly as you expect it.

Works in chai exactly as you expect it :

if (typeof define !== 'function') { var define = require('amdefine')(module); } // node only

define(
[
	'chai',
	'<class under test>',
	'extended-exceptions',
	'mocha'
],
function(chai, CUT, EE) {
	"use strict";

	var expect = chai.expect;
	chai.should();

	describe('Nice stuff', function() {

		describe('processing', function() {

			it('should detect bad state', function() {
				var out = CUT.make_new();

				var tempfn = function() { out.dostuff(); };
				tempfn.should.throw(EE.IllegalStateError, "Not initialized !"); // works fine
			});
		}); // describe feature
	}); // describe CUT
}); // requirejs module

Installation

Bower : bower install extended-exceptions.js Npm : npm install extended-exceptions

Unit tests

Browser : open test_runner/mocha.html Node : npm test