canirequire › CommonJS › unbox-primitive
Is unbox-primitive ESM-only? Can you require() it?
Unbox a boxed JS primitive value.
Last verified Sep 9, 2026 against unbox-primitive@1.1.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
unbox-primitive ships CommonJS only. require("unbox-primitive") 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 "unbox-primitive" 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("unbox-primitive") 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 unboxPrimitive from "unbox-primitive"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does unbox-primitive@1.1.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("unbox-primitive") from a CommonJS file and import "unbox-primitive" from an ES module.
| Runtime | require("unbox-primitive") | import "unbox-primitive" |
|---|---|---|
| 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 unbox-primitive
ES modules (import)
import unboxPrimitive from "unbox-primitive";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 unboxPrimitive = require("unbox-primitive");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 (4 versions; the newest 4 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.1.0 | CommonJS | Aug 11, 2019 |
Frequently asked
Is unbox-primitive ESM-only?
unbox-primitive@1.1.0 is a CommonJS package. unbox-primitive ships CommonJS only. require("unbox-primitive") 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 "unbox-primitive" 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 unbox-primitive with ES module syntax?
Yes. import unboxPrimitive from "unbox-primitive" 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 unbox-primitive work in Bun?
Yes. import "unbox-primitive" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does unbox-primitive ship TypeScript types?
Yes. unbox-primitive 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
- methods 1.1.2CommonJS
- jest-config 30.5.1Dual
- @protobufjs/pool 1.1.0CommonJS
- jest-docblock 30.5.0Dual
- unist-util-visit 5.1.0ESM-only
- fast-equals 6.0.3Dual
- wordwrap 1.0.0CommonJS
- test-exclude 8.0.0CommonJS