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

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

A JavaScript library that breaks strings into their individual user-perceived characters (including emojis!)

Last verified Sep 9, 2026 against graphemer@1.4.0.

graphemer ships CommonJS only. require("graphemer") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "graphemer" 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("graphemer") 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 graphemer from "graphemer"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: types are bundled; install nothing extra.

## Facts

- Latest: 1.4.0 (Sep 19, 2022)
- Module format: CommonJS
- Last CommonJS version: 1.4.0
- TypeScript types: bundled
- Node engines: not declared
- Weekly downloads: 38.9M
- License: MIT

## Runtime test results for graphemer@1.4.0

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

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

ES modules:

```js
import graphemer from "graphemer";
```

CommonJS:

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

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.4.0 | CommonJS | Sep 14, 2020 |

## Frequently asked

**Is graphemer ESM-only?**

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

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

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

**Does graphemer ship TypeScript types?**

Yes. graphemer bundles its own type declarations; no @types package is needed.

## Links

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