canirequire › CommonJS › nodeunit
Is nodeunit ESM-only? Can you require() it?
Easy unit testing for node.js and the browser.
Last verified Sep 9, 2026 against nodeunit@0.11.3. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
nodeunit ships CommonJS only. require("nodeunit") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "nodeunit" 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("nodeunit") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
- From ES modules use the default import: import nodeunit from "nodeunit"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/nodeunit
- This package is deprecated: you are strongly encouraged to use other testing options
Deprecated: you are strongly encouraged to use other testing options
Does nodeunit@0.11.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("nodeunit") from a CommonJS file and import "nodeunit" from an ES module.
| Runtime | require("nodeunit") | import "nodeunit" |
|---|---|---|
| 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 nodeunit
ES modules (import)
import nodeunit from "nodeunit";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 nodeunit = require("nodeunit");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 (48 versions; the newest 48 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 0.11.3 | CommonJS | Mar 4, 2011 |
Frequently asked
Is nodeunit ESM-only?
nodeunit@0.11.3 is a CommonJS package. nodeunit ships CommonJS only. require("nodeunit") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "nodeunit" 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 nodeunit with ES module syntax?
Yes. import nodeunit from "nodeunit" 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 nodeunit work in Bun?
Yes. import "nodeunit" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does nodeunit ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/nodeunit".
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
- jasmine-node 3.0.0CommonJS
- karma-browserify 8.1.0CommonJS
- dumi 2.4.49CommonJS
- babel-preset-latest 6.24.1CommonJS
- @storybook/addon-info 5.3.21CommonJS
- yeoman-assert 3.1.1CommonJS
- ember-cli-qunit 4.4.0CommonJS
- rollup-plugin-buble 0.19.8CommonJS