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

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

The string_decoder module from Node core

Last verified Sep 9, 2026 against string_decoder@1.3.0.

string_decoder ships CommonJS only. require("string_decoder") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "string_decoder" 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("string_decoder") 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 stringDecoder from "string_decoder"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: no types are available for string_decoder; declare the module yourself if you need them.

## Facts

- Latest: 1.3.0 (Aug 7, 2019)
- Module format: CommonJS
- Last CommonJS version: 1.3.0
- TypeScript types: none
- Node engines: not declared
- Weekly downloads: 227.8M
- License: MIT

## Runtime test results for string_decoder@1.3.0

Installed and executed on Sep 9, 2026 with require("string_decoder") from a CommonJS file and import "string_decoder" from an ES module.

| Runtime | require("string_decoder") | import "string_decoder" |
|---|---|---|
| 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 string_decoder

ES modules:

```js
import stringDecoder from "string_decoder";
```

CommonJS:

```js
const stringDecoder = require("string_decoder");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (14 versions; the newest 14 shown).

| Versions | Format | First published |
|---|---|---|
| 0.0.0 – 1.3.0 | CommonJS | Dec 3, 2013 |

## Frequently asked

**Is string_decoder ESM-only?**

string_decoder@1.3.0 is a CommonJS package. string_decoder ships CommonJS only. require("string_decoder") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "string_decoder" 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 string_decoder with ES module syntax?**

Yes. import stringDecoder from "string_decoder" 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 string_decoder work in Bun?**

Yes. import "string_decoder" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does string_decoder ship TypeScript types?**

No. string_decoder ships no type declarations and there is no @types package for it.

## Links

- [string_decoder on npm](https://www.npmjs.com/package/string_decoder)
- [Source repository](https://github.com/nodejs/string_decoder)
- [HTML version](https://canirequire.com/package/string_decoder/)
- [JSON version](https://canirequire.com/package/string_decoder.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.