canirequire › CommonJS › is-set
Is is-set ESM-only? Can you require() it?
Is this value a JS Set? This module works cross-realm/iframe, and despite ES6 @@toStringTag.
Last verified Sep 9, 2026 against is-set@2.0.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
is-set ships CommonJS only. require("is-set") 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-set" 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-set") 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 isSet from "is-set"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does is-set@2.0.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("is-set") from a CommonJS file and import "is-set" from an ES module.
| Runtime | require("is-set") | import "is-set" |
|---|---|---|
| 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-set
ES modules (import)
import isSet from "is-set";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 isSet = require("is-set");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 (5 versions; the newest 5 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 2.0.3 | CommonJS | Feb 18, 2015 |
Frequently asked
Is is-set ESM-only?
is-set@2.0.3 is a CommonJS package. is-set ships CommonJS only. require("is-set") 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-set" 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-set with ES module syntax?
Yes. import isSet from "is-set" 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-set work in Bun?
Yes. import "is-set" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does is-set ship TypeScript types?
Yes. is-set 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
- @pkgjs/parseargs 0.11.0CommonJS
- @floating-ui/react-dom 2.1.9Dual
- for-each 0.3.5CommonJS
- normalize-path 3.0.0CommonJS
- bl 7.0.12ESM-only
- sprintf-js 1.1.3CommonJS
- arraybuffer.prototype.slice 1.0.4CommonJS
- @smithy/util-utf8 4.5.2CommonJS