canirequire › CommonJS › pino
Is pino ESM-only? Can you require() it?
super fast, all natural json logger
Last verified Sep 9, 2026 against pino@10.3.1. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
pino ships CommonJS only. require("pino") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "pino" 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("pino") 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 pino from "pino"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does pino@10.3.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("pino") from a CommonJS file and import "pino" from an ES module.
| Runtime | require("pino") | import "pino" |
|---|---|---|
| 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 pino
ES modules (import)
import pino from "pino";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 pino = require("pino");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 (316 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 8.6.0 – 10.3.1 | CommonJS | Sep 19, 2022 |
Frequently asked
Is pino ESM-only?
pino@10.3.1 is a CommonJS package. pino ships CommonJS only. require("pino") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "pino" 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 pino with ES module syntax?
Yes. import pino from "pino" 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 pino work in Bun?
Yes. import "pino" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does pino ship TypeScript types?
Yes. pino 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
- @opentelemetry/sdk-metrics 2.11.0CommonJS
- make-error 1.3.6CommonJS
- @istanbuljs/schema 0.1.6CommonJS
- lodash.debounce 4.0.8CommonJS
- jest-runner 30.5.1Dual
- expect 30.5.1Dual
- @octokit/openapi-types 29.0.1No entry
- serialize-javascript 7.1.1CommonJS