canirequire › CommonJS › opn
Is opn ESM-only? Can you require() it?
Open stuff like URLs, files, executables. Cross-platform.
Last verified Sep 9, 2026 against opn@6.0.0. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
opn ships CommonJS only. require("opn") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8. import "opn" 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("opn") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8.
- From ES modules use the default import: import opn from "opn"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/opn
- This package is deprecated: The package has been renamed to `open`
Deprecated: The package has been renamed to `open`
Does opn@6.0.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("opn") from a CommonJS file and import "opn" from an ES module.
| Runtime | require("opn") | import "opn" |
|---|---|---|
| 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 opn
ES modules (import)
import opn from "opn";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 opn = require("opn");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 (22 versions; the newest 22 shown).
| Versions | Format | First published |
|---|---|---|
| 0.1.0 – 6.0.0 | CommonJS | Apr 5, 2014 |
Frequently asked
Is opn ESM-only?
opn@6.0.0 is a CommonJS package. opn ships CommonJS only. require("opn") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=8. import "opn" 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 opn with ES module syntax?
Yes. import opn from "opn" 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 opn work in Bun?
Yes. import "opn" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does opn ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/opn".
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-loader 4.0.2CommonJS
- react-dev-utils 12.0.1No entry
- @angular/compiler-cli 22.1.5ESM-only
- @storybook/builder-webpack5 10.6.0ESM-only
- requirejs 2.3.8CommonJS
- c8 12.0.0CommonJS
- eslint-plugin-flowtype 8.0.3CommonJS
- @angular/animations 22.1.5ESM-only