node-domexception
npmv2.0.2DeprecatedAn implementation of the DOMException class from NodeJS
Deprecation notice: Use your platform's native DOMException instead
Not recommended for new projects
No — node-domexception should not be adopted for new projects. Explicitly marked deprecated by its publisher.
- AAdoption: grade A, Excellent.
45.9M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Explicitly marked deprecated by its publisher.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 5.3 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding node-domexception to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=16
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the node-domexception README.
import 'node-domexception'
// You could also do conditional import.
globalThis.DOMException || await import('node-domexception')
/********************************************************************/
import { MessageChannel } from 'worker_threads'
try {
const port = new MessageChannel().port1
const ab = new ArrayBuffer()
port.postMessage(ab, [ab, ab])
} catch (err) {Used by
Popular packages that depend on node-domexception.
Relationship graph
Dependencies (left) and dependents (right) of node-domexception.
Frequently installed together
Release history
1 release in the last two years, typically about 642 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.2latest | 1 year ago | 5.3 KB | MIT |
| 2.0.1 | 3 years ago | 5.0 KB | MIT |
| 2.0.0 | 3 years ago | 5.3 KB | MIT |
| 1.0.0 | 5 years ago | 28 KB | MIT |
Overview
node-domexception is a deprecated npm package that an implementation of the DOMException class from NodeJS. It is extremely widely used, with about 45.9M downloads per week and 1 known dependents in the graph. The latest version is 2.0.2, released under the MIT license.
Who should use it
node-domexception is deprecated and is best avoided for new projects. Existing users should plan a migration to a maintained alternative.
When not to use it
Do not adopt this package for new work — it is no longer maintained.
Pros
- Large, well-established user base (45.9M weekly downloads).
- Clear open-source license (MIT).
- Zero runtime dependencies — minimal footprint.
Cons
- Marked deprecated: Use your platform's native DOMException instead.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use node-domexception?
No — node-domexception should not be adopted for new projects. Explicitly marked deprecated by its publisher.
How do I install node-domexception?
Run `npm install node-domexception` to add node-domexception to your npm project.
What license is node-domexception released under?
node-domexception is distributed under the MIT license.
How popular is node-domexception?
node-domexception has approximately 45,899,210 downloads per week and 1 known dependent packages.
Is node-domexception still maintained?
No — node-domexception is marked as deprecated: Use your platform's native DOMException instead. Consider a maintained alternative for new projects.
Does node-domexception run install scripts?
No. node-domexception does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.