canirequire › CommonJS › is-map
Is is-map ESM-only? Can you require() it?
Is this value a JS Map? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Last verified Sep 9, 2026 against is-map@2.0.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
is-map ships CommonJS only. require("is-map") 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 "is-map" 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("is-map") 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 isMap from "is-map"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does is-map@2.0.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("is-map") from a CommonJS file and import "is-map" from an ES module.
| Runtime | require("is-map") | import "is-map" |
|---|---|---|
| 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 is-map
ES modules (import)
import isMap from "is-map";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 isMap = require("is-map");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 (6 versions; the newest 6 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 2.0.3 | CommonJS | Feb 18, 2015 |
Frequently asked
Is is-map ESM-only?
is-map@2.0.3 is a CommonJS package. is-map ships CommonJS only. require("is-map") 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 "is-map" 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 is-map with ES module syntax?
Yes. import isMap from "is-map" 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 is-map work in Bun?
Yes. import "is-map" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does is-map ship TypeScript types?
Yes. is-map bundles its own type declarations; no @types package is needed.
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
- serialize-javascript 7.1.1CommonJS
- nwsapi 2.2.27CommonJS
- jest-leak-detector 30.5.1Dual
- @babel/plugin-syntax-import-attributes 7.29.7CommonJS
- http-cache-semantics 4.2.0CommonJS
- @babel/plugin-transform-parameters 8.0.1ESM-only
- @babel/plugin-transform-block-scoping 8.0.1ESM-only
- typed-array-byte-length 1.0.3CommonJS