canirequire › CommonJS › string.prototype.matchall
Is string.prototype.matchall ESM-only? Can you require() it?
Spec-compliant polyfill for String.prototype.matchAll
Last verified Sep 9, 2026 against string.prototype.matchall@4.1.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
string.prototype.matchall ships CommonJS only. require("string.prototype.matchall") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "string.prototype.matchall" 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("string.prototype.matchall") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4.
- From ES modules use the default import: import stringPrototypeMatchall from "string.prototype.matchall"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/string.prototype.matchall
Does string.prototype.matchall@4.1.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("string.prototype.matchall") from a CommonJS file and import "string.prototype.matchall" from an ES module.
| Runtime | require("string.prototype.matchall") | import "string.prototype.matchall" |
|---|---|---|
| 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 string.prototype.matchall
ES modules (import)
import stringPrototypeMatchall from "string.prototype.matchall";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 stringPrototypeMatchall = require("string.prototype.matchall");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 (19 versions; the newest 19 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 4.1.0 | CommonJS | Sep 28, 2017 |
Frequently asked
Is string.prototype.matchall ESM-only?
string.prototype.matchall@4.1.0 is a CommonJS package. string.prototype.matchall ships CommonJS only. require("string.prototype.matchall") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "string.prototype.matchall" 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 string.prototype.matchall with ES module syntax?
Yes. import stringPrototypeMatchall from "string.prototype.matchall" 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 string.prototype.matchall work in Bun?
Yes. import "string.prototype.matchall" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does string.prototype.matchall ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/string.prototype.matchall".
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
- unist-util-is 6.0.1ESM-only
- typed-array-byte-offset 1.0.4CommonJS
- lz-string 1.5.0CommonJS
- unist-util-visit-parents 6.0.2ESM-only
- is-weakset 2.0.4CommonJS
- autoprefixer 10.5.5CommonJS
- bn.js 5.2.5CommonJS
- pirates 4.0.7CommonJS