canirequire › CommonJS › set-function-name
Is set-function-name ESM-only? Can you require() it?
Set a function's name property
Last verified Sep 9, 2026 against set-function-name@2.0.2. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
set-function-name ships CommonJS only. require("set-function-name") 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 "set-function-name" 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("set-function-name") 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 setFunctionName from "set-function-name"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does set-function-name@2.0.2 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("set-function-name") from a CommonJS file and import "set-function-name" from an ES module.
| Runtime | require("set-function-name") | import "set-function-name" |
|---|---|---|
| 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 set-function-name
ES modules (import)
import setFunctionName from "set-function-name";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 setFunctionName = require("set-function-name");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 – 2.0.2 | CommonJS | Sep 14, 2017 |
Frequently asked
Is set-function-name ESM-only?
set-function-name@2.0.2 is a CommonJS package. set-function-name ships CommonJS only. require("set-function-name") 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 "set-function-name" 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 set-function-name with ES module syntax?
Yes. import setFunctionName from "set-function-name" 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 set-function-name work in Bun?
Yes. import "set-function-name" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does set-function-name ship TypeScript types?
Yes. set-function-name 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
- micromark-util-character 2.1.1ESM-only
- buffer-from 1.1.2CommonJS
- @tailwindcss/oxide 4.3.3CommonJS
- get-nonce 1.0.1CommonJS
- cssstyle 6.2.0CommonJS
- @octokit/types 18.0.0No entry
- fast-xml-parser 5.11.1Dual
- @aws-sdk/xml-builder 3.972.40CommonJS