abort-controller
npmv3.0.0An implementation of WHATWG AbortController interface.
Not recommended for new projects
No — abort-controller should not be adopted for new projects. Last published 2720 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2720 days ago.
- AWeight: grade A, Excellent.
Pulls in 1 transitive package, about 456 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 abort-controller 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.
Licenses in the dependency tree
Every license you inherit by installing abort-controller, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=6.5
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the abort-controller README.
import AbortController from "abort-controller"
const controller = new AbortController()
const signal = controller.signal
signal.addEventListener("abort", () => {
console.log("aborted!")
})
controller.abort()abort-controller vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| abort-controllerthis page | 0 | 4 | MIT | 7 years ago |
| event-target-shim | 0 | 2 | MIT | 1 day ago |
| happy-dom | 0 | 6 | MIT | 1 day ago |
| jsdom | 0 | 20 | MIT | 1 day ago |
| tr46 | 192.6M | 1 | MIT | 1 day ago |
| node-fetch | 172.9M | 9 | MIT | 1 day ago |
Dependencies
Declared by abort-controller v3.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (36)
Used by
Popular packages that depend on abort-controller.
A light-weight module that brings Fetch API to node.js
An HTTP/1.1 client, written from scratch for Node.js
A framework for building native apps using React
An implementation of window.fetch in Node.js using Minipass streams
Relationship graph
Dependencies (left) and dependents (right) of abort-controller.
Frequently installed together
An extremely fast JavaScript and CSS bundler and minifier.
An AST-based pattern checker for JavaScript.
Delightful JavaScript Testing.
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Fake JavaScript timers
TypeScript definitions for node
the complete solution for node.js command-line programs
React is a JavaScript library for building user interfaces.
A memoization library which only remembers the latest invocation
A low level parser for ANSI sequences.
Cooperative scheduler for the browser environment.
Convert character encodings in pure javascript.
Release history
No releases in the last two years, typically about 43 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.0.0latest | 7 years ago | 75 KB | MIT |
| 2.0.3 | 7 years ago | 73 KB | MIT |
| 2.0.2 | 7 years ago | 73 KB | MIT |
| 2.0.1 | 7 years ago | 73 KB | MIT |
| 2.0.0 | 7 years ago | 76 KB | MIT |
| 1.1.0 | 7 years ago | 71 KB | MIT |
| 1.1.0-beta.0 | 8 years ago | 71 KB | MIT |
| 1.0.2 | 8 years ago | 70 KB | MIT |
| 1.0.1 | 8 years ago | 66 KB | MIT |
| 1.0.0 | 9 years ago | — | MIT |
| 0.0.0 | 9 years ago | — | MIT |
Overview
abort-controller is an npm package that an implementation of WHATWG AbortController interface. It has 4 known dependents in the graph. The latest version is 3.0.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need an implementation of WHATWG AbortController interface and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- Large dependency tree (37 direct dependencies) increases install size and audit surface.
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use abort-controller?
No — abort-controller should not be adopted for new projects. Last published 2720 days ago.
How do I install abort-controller?
Run `npm install abort-controller` to add abort-controller to your npm project.
How many dependencies does abort-controller have?
abort-controller declares 37 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 456 KB on disk.
What license is abort-controller released under?
abort-controller is distributed under the MIT license.
How popular is abort-controller?
npm does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on abort-controller.
Is abort-controller still maintained?
The most recent release of abort-controller (v3.0.0) was published 7 years ago.
Does abort-controller run install scripts?
No. abort-controller does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.