# Is pino ESM-only? Can you require() it?

> pino@10.3.1 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

super fast, all natural json logger

Last verified Sep 9, 2026 against pino@10.3.1.

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

1. require("pino") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
2. 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.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 10.3.1 (Feb 9, 2026)
- Module format: CommonJS
- Last CommonJS version: 10.3.1
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 43.8M
- License: MIT

## Runtime test results for pino@10.3.1

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:

```js
import pino from "pino";
```

CommonJS:

```js
const pino = require("pino");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (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

- [pino on npm](https://www.npmjs.com/package/pino)
- [Source repository](https://github.com/pinojs/pino)
- [HTML version](https://canirequire.com/package/pino/)
- [JSON version](https://canirequire.com/package/pino.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.