canirequire › CommonJS › browserify
Is browserify ESM-only? Can you require() it?
browser-side require() the node way
Last verified Sep 9, 2026 against browserify@17.0.1. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
browserify ships CommonJS only. require("browserify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8. import "browserify" 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("browserify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8.
- From ES modules use the default import: import browserify from "browserify"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: npm install -D @types/browserify
Does browserify@17.0.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("browserify") from a CommonJS file and import "browserify" from an ES module.
| Runtime | require("browserify") | import "browserify" |
|---|---|---|
| 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 browserify
ES modules (import)
import browserify from "browserify";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 browserify = require("browserify");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 (485 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 8.1.0 – 17.0.1 | CommonJS | Jan 9, 2015 |
Frequently asked
Is browserify ESM-only?
browserify@17.0.1 is a CommonJS package. browserify ships CommonJS only. require("browserify") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8. import "browserify" 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 browserify with ES module syntax?
Yes. import browserify from "browserify" 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 browserify work in Bun?
Yes. import "browserify" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does browserify ship TypeScript types?
Not bundled. Install the community types with "npm install -D @types/browserify".
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
- babel-register 6.26.0CommonJS
- crypto 1.0.1CommonJS
- react-bootstrap 2.10.10CommonJS
- lerna 10.0.1ESM-only
- pretty-quick 4.2.2Dual
- chai-as-promised 8.0.2ESM-only
- @angular/language-service 22.1.5CommonJS
- @vue/eslint-config-typescript 14.9.0Dual