canirequire › CommonJS › abort-controller
Is abort-controller ESM-only? Can you require() it?
An implementation of WHATWG AbortController interface.
Last verified Sep 9, 2026 against abort-controller@3.0.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
abort-controller ships CommonJS only. require("abort-controller") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.5. import "abort-controller" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
What to do
- require("abort-controller") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.5.
- From ES modules use the default import: import abortController from "abort-controller"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for abort-controller; declare the module yourself if you need them.
Does abort-controller@3.0.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("abort-controller") from a CommonJS file and import "abort-controller" from an ES module.
| Runtime | require("abort-controller") | import "abort-controller" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4.0 | ✓ works | ✓ works |
How to import abort-controller
ES modules (import)
import abortController from "abort-controller";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const abortController = require("abort-controller");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (10 versions; the newest 10 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 3.0.0 | CommonJS | Sep 29, 2017 |
Frequently asked
Is abort-controller ESM-only?
abort-controller@3.0.0 is a CommonJS package. abort-controller ships CommonJS only. require("abort-controller") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.5. import "abort-controller" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import abort-controller with ES module syntax?
Yes. import abortController from "abort-controller" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does abort-controller work in Bun?
Yes. import "abort-controller" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does abort-controller ship TypeScript types?
No. abort-controller ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- neo-async 2.6.2CommonJS
- jest-resolve 30.5.1Dual
- decompress-response 10.0.0ESM-only
- jest-watcher 30.5.1Dual
- @aws-sdk/util-endpoints 3.996.43CommonJS
- @img/sharp-libvips-linuxmusl-x64 1.3.3CommonJS
- color 5.0.3ESM-only
- @img/sharp-linuxmusl-x64 0.35.4CommonJS