The node-domexception package provides a way to handle DOMException objects in Node.js environments, similar to how they are handled in web browsers. This package is useful for projects that need to simulate browser-like handling of exceptions, particularly in testing environments or server-side applications that interact with web APIs.

What are node-domexception's main functionalities?

Creating DOMException objects

This feature allows developers to create instances of DOMException with a custom message and name, mimicking the behavior seen in web browsers. It is particularly useful for throwing and catching specific types of exceptions in Node.js applications.

const DOMException = require('node-domexception');

const exception = new DOMException('An error occurred', 'NotFoundError');
console.log(exception.name); // Outputs: NotFoundError
console.log(exception.message); // Outputs: An error occurred

Checking instance of DOMException

This feature enables developers to check if an object is an instance of DOMException. This is useful for error handling and control flow in applications that need to differentiate between exception types.

const DOMException = require('node-domexception');

const exception = new DOMException('Failed operation', 'SecurityError');
if (exception instanceof DOMException) {
  console.log('Caught a DOMException');
}

Other packages similar to node-domexception

Readme

Source

DOMException

An implementation of the DOMException class from NodeJS

NodeJS has DOMException built in, but it's not globally available, and you can't require/import it from somewhere.

This package exposes the DOMException class that comes from NodeJS itself. (including all of the legacy codes)

_{(plz don't depend on this package in any other environment other than node >=10.5)}

import DOMException from 'node-domexception'
import { MessageChannel } from 'worker_threads'

async function hello() {
  const port = new MessageChannel().port1
  const ab = new ArrayBuffer()
  port.postMessage(ab, [ab, ab])
}

hello().catch(err => {
  console.assert(err.name === 'DataCloneError')
  console.assert(err.code === 25)
  console.assert(err instanceof DOMException)
})

const e1 = new DOMException('Something went wrong', 'BadThingsError')
console.assert(e1.name === 'BadThingsError')
console.assert(e1.code === 0)

const e2 = new DOMException('Another exciting error message', 'NoModificationAllowedError')
console.assert(e2.name === 'NoModificationAllowedError')
console.assert(e2.code === 7)

console.assert(DOMException.INUSE_ATTRIBUTE_ERR === 10)

Background

The only possible way is to use some web-ish tools that have been introduced into NodeJS that throws a DOMException and catch the constructor. This is exactly what this package dose for you and exposes it.
This way you will have the same class that NodeJS has and you can check if the error is a instance of DOMException.
The instanceof check would not have worked with a custom class such as the DOMException provided by domenic which also is much larger in size since it has to re-construct the hole class from the ground up.

The DOMException is used in many places such as the Fetch API, File & Blobs, PostMessaging and more.
Why they decided to call it DOM, I don't know

Please consider sponsoring if you find this helpful

FAQs

What is node-domexception?

Is node-domexception well maintained?

Last updated on 27 May 2021

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install