canirequire › CommonJS › gensync
Is gensync ESM-only? Can you require() it?
Allows users to use generators in order to write common functions that can be both sync or async.
Last verified Sep 9, 2026 against gensync@1.0.0-beta.2. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
gensync ships CommonJS only. require("gensync") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.9.0. import "gensync" 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("gensync") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.9.0.
- From ES modules use the default import: import gensync from "gensync"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/gensync
Does gensync@1.0.0-beta.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("gensync") from a CommonJS file and import "gensync" from an ES module.
| Runtime | require("gensync") | import "gensync" |
|---|---|---|
| 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 gensync
ES modules (import)
import gensync from "gensync";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 gensync = require("gensync");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 (1 versions; the newest 1 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 | CommonJS | Nov 23, 2015 |
Frequently asked
Is gensync ESM-only?
gensync@1.0.0-beta.2 is a CommonJS package. gensync ships CommonJS only. require("gensync") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=6.9.0. import "gensync" 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 gensync with ES module syntax?
Yes. import gensync from "gensync" 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 gensync work in Bun?
Yes. import "gensync" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does gensync ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/gensync".
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
- raw-body 4.0.0ESM-only
- @opentelemetry/core 2.11.0CommonJS
- @typescript-eslint/types 8.70.0CommonJS
- content-disposition 3.0.0ESM-only
- send 1.2.1CommonJS
- y18n 5.0.8Dual
- path-scurry 2.0.2Dual
- acorn-jsx 5.3.2CommonJS